Udp broadcast for a user interface in a download and configuration gaming method

ABSTRACT

A system and method are disclosed for implementing a modified form of User Datagram Protocol (UDP) multicast notification system in a client-server architecture that otherwise allows only client initiated messages. The method includes: receiving a registration message at a server from a client with a client IP address in the registration message, wherein the registration message includes types of notifications desired to be received by the client, and wherein the server is a Download and Configuration Management (DCM) engine; adding the client IP address to a list in a registration message database; receiving a request for a port number by the client; and responding with the port number to the client.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.12/691,667, filed Jan. 21, 2010 entitled UDP BROADCAST FOR A USERINTERFACE IN A DOWNLOAD AND CONFIGURATION GAMING METHOD, which is adivisional of U.S. patent application Ser. No. 12/113,178, filed Apr.30, 2008, entitled UDP BROADCAST FOR A USER INTERFACE IN A DOWNLOAD ANDCONFIGURATION GAMING METHOD, now U.S. Pat. No. 7,730,198, issued Jun. 1,2010, which is hereby incorporated by reference in its entirety.

U.S. patent application Ser. No. 12/113,178 is also acontinuation-in-part of U.S. patent application Ser. No. 11/983,121filed Nov. 9, 2007, entitled GAMING SYSTEM DOWNLOAD NETWORKARCHITECTURE, (Atty. Docket. No. 110184.454), which claims benefit under35 U.S.C. §119(e) to U.S. provisional patent application Ser. No.60/865,332, filed Nov. 10, 2006; and to U.S. provisional patentapplication Ser. No. 60/865,550, filed Nov. 13, 2006. U.S. patentapplication Ser. No. 12/113,178 is also a continuation-in-part of U.S.patent application Ser. No. 11/938,228 filed Nov. 9, 2007 and entitled“GAMING SYSTEM CONFIGURATION CHANGE REPORTING” (Atty. Docket. No.110184.45401). U.S. patent application Ser. No. 12/113,178 is also acontinuation-in-part of U.S. patent application Ser. No. 11/938,155filed Nov. 9, 2007 and entitled “REPORTING FUNCTION IN GAMING SYSTEMENVIRONMENT” (Atty. Docket. No. 110184.45402). U.S. patent applicationSer. No. 12/113,178 is also a continuation-in-part of U.S. patentapplication Ser. No. 11/938,190 filed Nov. 9, 2007 and entitled “SECURECOMMUNICATIONS IN GAMING SYSTEM” (Atty. Docket. No. 110184.45403). U.S.patent application Ser. No. 12/113,178 is also a continuation-in-part ofU.S. patent application Ser. No. 11/938,163 filed Nov. 9, 2007 andentitled “METHODS AND SYSTEMS FOR CONTROLLING ACCESS TO RESOURCES IN AGAMING NETWORK” (Atty. Docket. No. 110184.45404), all of which arehereby incorporated by reference in their entirety.

This application is also related to U.S. patent application Ser. No.12/113,173 filed Apr. 30, 2008. This application is also related to U.S.patent application Ser. No. 12/113,095 filed Apr. 30, 2008. Thisapplication is also related to U.S. patent application Ser. No.12/113,105 filed Apr. 30, 2008.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

FIELD

This disclosure pertains generally to management systems and methods.More particularly, this disclosure relates to a computerized method andsystem for downloading gaming software and configuring gaming machines.

BACKGROUND

Various networked gaming systems have been developed over the yearsbeginning at least in the 1980's. With acceptance and utilization, userssuch as casino operators have found it desirable to increase thecomputer management of their facilities and expand features available onnetworked gaming systems. For instance, there are various areas in themanagement of casinos that is very labor intensive, such asreconfiguring gaming machines, changing games on the gaming machines,and performing cash transactions for customers.

Until recently, the gaming industry has been a collection of proprietarysystems and communication protocols. In many cases, a casino had to buythe entire system (games, controllers, backend systems, and the like)from one company. Most casinos would prefer to use a mix of differentmanufacturer's games on the gaming floor, and then pick the best backendsystem that suits their needs. Until recently, this was not a realisticexpectation.

A few years ago, several gaming entities formed the Gaming StandardsAssociation (GSA) to define standardized protocols by which games,gaming controllers, and backend systems could communicate. This allowsinteroperability of different manufacturer's equipment, as well asgiving the casinos the freedom to choose whatever manufacturers theywant for the various components of a gaming system. One of the GSAprotocols is the Game-to-System (G2S) protocol, which is designed todefine the messages between a gaming machine and a backend system. Thisprotocol does include messages for handling software download andconfiguration of the gaming machines.

The introduction of download and configuration capabilities in thegaming environment creates considerable operational challenges.Downloading typically requires a considerable volume of gaming contentto be transferred over the network. Many casinos are open twenty fourhours a day, seven days a week, which requires downloading to take placewithout disrupting normal gaming activities. Accordingly, in somecircumstances it may be necessary to limit download bandwidth, at theexpense of download time, in order to not overly tax the networkresources. Thus, a way of easily monitoring download progress would beinvaluable to casino operators.

In one configuration, a download system may be centralized and “push”the data down to the games. In this case, the content server knows howmuch has been downloaded at any time. However, in a “pull” system, wherethe gaming devices are told where to go for the data and the games aretaking (“pulling”) the data from the content server, the servergenerally does not know how much data a given game has downloaded. Thus,a way is needed for the games to keep the download management systemappraised of how far along they are in the download process.

SUMMARY

In one aspect of the invention, a computerized download andconfiguration server-based system and method for use with game devices,systems, and methods is provided to enable users to monitor, control,and modify game devices and other related activities.

In another embodiment, a method is also disclosed for implementing amodified form of User Datagram Protocol (UDP) multicast notificationsystem in a client-server architecture that otherwise allows onlyclient-initiated messages. The method includes: receiving a registrationmessage from a client with a client IP address in the registrationmessage, wherein the registration message includes types ofnotifications desired to be received by the client, and wherein theserver is a Download and Configuration Management (DCM) engine; addingthe client IP address to a list in a registration message database;receiving a request for a port number by the client; and responding withthe port number to the client.

In another embodiment, a system for sending a notification message usinga modified form of User Datagram Protocol (UDP) multicast notificationsystem in a client-server architecture that otherwise allows only clientinitiated messages. The system includes a plurality of clients(configured in a client-server architecture) and a server. The serverincludes one or more processors executing software instructions thatperform the steps of: receiving a registration message from a clientwith a client IP address in the registration message, wherein theregistration message includes types of notifications desired to bereceived by the client, and wherein the server is a Download andConfiguration Management (DCM) engine; adding the client IP address to alist in a registration message database; receiving a request for a portnumber by the client; and responding with the port number to the client.

In a further embodiment, yet another system is disclosed forimplementing a modified form of User Datagram Protocol (UDP) multicastnotification system in a client-server architecture. The systemincludes: means for receiving a registration message at a server from aclient with a client IP address in the registration message, wherein theregistration message includes types of notifications desired to bereceived by the client, and wherein the server is a Download andConfiguration Management (DCM) engine; means for adding the client IPaddress to a list in a registration message database; means forreceiving a request for a port number by the client; and means forresponding with the port number to the client.

Further aspects, features and advantages of various embodiments of theinvention will be apparent from the following detailed disclosure, takenin conjunction with the accompanying sheets of drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, identical reference numbers identify similar elementsor acts. The sizes and relative positions of elements in the drawingsare not necessarily drawn to scale. For example, the shapes of variouselements and angles are not drawn to scale, and some of these elementsare arbitrarily enlarged and positioned to improve drawing legibility.Further, the particular shapes of the elements as drawn, are notintended to convey any information regarding the actual shape of theparticular elements, and have been solely selected for ease ofrecognition in the drawings.

FIG. 1 is a block diagram of a slot management system, according to oneillustrated embodiment.

FIGS. 2A(1)-2A(2) are a context diagram of operation of a downloadconfiguration server system according to one illustrated embodiment.

FIG. 2B is a tiered layer diagram of a download and configuration systemarchitecture, according to one illustrated embodiment.

FIGS. 2C(1) and 2C(2) are a block diagram showing various components ofa download and configuration system architecture, according to oneillustrated embodiment.

FIG. 2D is a schematic diagram of a download and configuration network,according to one illustrated embodiment.

FIG. 2E is a schematic diagram showing a download and configurationnetwork, according to one illustrated embodiment.

FIG. 3 is a flow diagram showing a download and configuration user treelogic, according to one illustrated embodiment.

FIG. 4 is a flow diagram showing a download and configuration user treelogic to manage a package library (SDDP), according to one illustratedembodiment.

FIG. 5 is a flow diagram showing a download and configuration user treelogic to manage downloads, according to one illustrated embodiment.

FIG. 6 is a flow diagram showing a download and configuration user treelogic to edit download assignments, according to one illustratedembodiment.

FIG. 7 is a flow diagram showing a download and configuration user treelogic to manage a collection, according to one illustrated embodiment.

FIG. 8 is a flow diagram showing a download and configuration user treelogic to download views, according to one illustrated embodiment.

FIG. 9 is a flow diagram showing a download and configuration user treelogic to manage configurations, according to one illustrated embodiment.

FIG. 10 is a flow diagram showing a download and configuration user treelogic to edit configuration assignments, according to one illustratedembodiment.

FIG. 11 is a flow diagram showing a download and configuration user treelogic of various configuration views, according to one illustratedembodiment.

FIG. 12 is a flow diagram showing a download and configuration user treelogic to manage reports, according to one illustrated embodiment.

FIG. 13 is a flow diagram showing a download and configuration user treelogic to interact with various electronic game machines (EGMs) 213,according to one illustrated embodiment.

FIG. 14 is a flow diagram showing a download and configuration user treelogic to execute configuration jobs, according to one illustratedembodiment.

FIG. 15 is a flow diagram showing a download and configuration user treelogic to execute download jobs, according to one illustrated embodiment.

FIG. 16 is a flow diagram showing a method of handling download andconfiguration messages, according to one illustrated embodiment.

FIG. 17 is a flow diagram showing a method of downloading packages,according to one illustrated embodiment.

FIG. 18 is a block diagram showing various components of a DCL controlpanel, according to one illustrated embodiment.

FIG. 19 is a block diagram showing a download handler, according to oneillustrated embodiment.

FIG. 20 is a block diagram showing a configuration handler, according toone illustrated embodiment.

FIG. 21 is a block diagram illustrating a scheduler service, accordingto one illustrated embodiment.

FIG. 22 is a block diagram illustrating a user interface download Webservice, according to one illustrated embodiment.

FIG. 23 is a block diagram illustrating a user interface configurationWeb service, according to one illustrated embodiment.

FIG. 24 is a block diagram illustrating a scheduler Web service,according to one illustrated embodiment.

FIG. 25 is a block diagram showing an executive unit, according to oneillustrated embodiment.

FIG. 26 is a block diagram illustrating a download handler Web service,according to one illustrated embodiment.

FIG. 27 is a block diagram illustrating an option configuration handlerWeb service, according to one illustrated embodiment.

FIG. 28A is a flow diagram illustrating a method of viewing packages,according to one illustrated embodiment.

FIG. 28B is a flow diagram illustrating a method of viewing packagemodules, according to one illustrated embodiment.

FIG. 28C is a flow diagram illustrating a method of viewing packagemanagement logs, according to one illustrated embodiment.

FIG. 29 is a flow diagram illustrating a method of creating a downloadassignment, according to one illustrated embodiment.

FIG. 30 is a flow diagram illustrating a method of creating aconfiguration assignment, according to one illustrated embodiment.

FIG. 31 is a flow diagram illustrating a method of initiating a packageinstallation, according to one illustrated embodiment.

FIG. 32 is a flow diagram illustrating a method of editing a downloadassignment, according to one illustrated embodiment.

FIG. 33 is a flow diagram illustrating a method of editing aconfiguration assignment, according to one illustrated embodiment.

FIG. 34 is a flow diagram illustrating a method of performing an EGMconfiguration discovery, according to one illustrated embodiment.

FIG. 35 is a flow diagram illustrating a method of performing an EGMdownload discovery, according to one illustrated embodiment.

FIG. 36 is a flow diagram illustrating a method of obtaining aconfiguration, according to one illustrated embodiment.

FIG. 37 is a flow diagram illustrating a method of refreshing aninventory, according to one illustrated embodiment.

FIG. 38 is a flow diagram illustrating a method of obtaining aninventory job, according to one illustrated embodiment.

FIG. 39 is a flow diagram illustrating a method of setting configurationchanges jobs, according to one illustrated embodiment.

FIG. 40 is a flow diagram illustrating a method of cancelling an optionchange, according to one illustrated embodiment.

FIG. 41 is a flow diagram illustrating a method of performing anunsolicited options list, according to one illustrated embodiment.

FIG. 42 is a flow diagram illustrating a method of performing anunsolicited options change status, according to one illustratedembodiment.

FIG. 43 is a flow diagram illustrating a method of downloading apackage, according to one illustrated embodiment.

FIG. 44 is a flow diagram illustrating a method of installing a package,according to one illustrated embodiment.

FIG. 45 is a flow diagram illustrating a method of cancelling a pendingdownload of a package, according to one illustrated embodiment.

FIG. 46 is a flow diagram illustrating a method of scheduling a jobexecution, according to one illustrated embodiment.

FIG. 47A is a flow diagram illustrating a method of managing packages,according to one illustrated embodiment.

FIG. 47B is a flow diagram illustrating a method of performing a packagemanagement system configuration, according to one illustratedembodiment.

FIGS. 48A-48L are a block diagram of a download ERD, according to oneillustrated embodiment.

FIGS. 49A-49I are a block diagram of a configuration ERD, according toone illustrated embodiment.

FIG. 50 is a block diagram of a schedule ERD, according to oneillustrated embodiment.

FIG. 51A is a screen print of a download and configuration controlpanel, according to one illustrated embodiment.

FIG. 51B is a screen print of a login control panel, according to oneillustrated embodiment.

FIG. 51C is a screen print of a change login password control panel,according to one illustrated embodiment.

FIG. 51D is an EGM navigation control panel, according to oneillustrated embodiment.

FIG. 51E is a screen print of a collection navigator control panel,according to one illustrated embodiment.

FIG. 51F is a screen print of an assignment navigator control panel,according to one illustrated embodiment.

FIG. 51G is a screen print of a manual override control panel, accordingto one illustrated embodiment.

FIG. 51H is a screen print of an inventory control panel, according toone illustrated embodiment.

FIG. 51I is a screen print of a search, query and display control panel,according to one illustrated embodiment.

FIG. 51J is a screen print of an activity log query and display controlpanel, according to one illustrated embodiment.

FIG. 52A is a screen print of a download wizard control panel to assistin choosing EGMs, according to one illustrated embodiment.

FIG. 52B is a screen print of a download wizard control panel assist inchoosing packages, according to one illustrated embodiment.

FIG. 52C is a screen print of a download wizard control panel assist inscheduling changes, according to one illustrated embodiment.

FIG. 52D is a screen print of a download wizard control panel assist inreviewing assignments, according to one illustrated embodiment.

FIG. 53A is a screen print of a configuration assignment wizard controlpanel assist in choosing EGMs, according to one illustrated embodiment.

FIG. 53B is a screen print of a configuration assignment wizard controlpanel assist in choosing options, according to one illustratedembodiment.

FIG. 53C is a screen print of a configuration assignment wizard controlpanel assist in choosing game options, according to one illustratedembodiment.

FIG. 53D is a screen print of a configuration assignment wizard controlpanel assist in making schedule changes, according to one illustratedembodiment.

FIG. 53E is a screen print of a configuration assignment wizard controlpanel assist in choosing reviewing assignments, according to oneillustrated embodiment.

FIG. 54A is a screen print of a floor layout control panel, according toone illustrated embodiment.

FIG. 54B is a screen print of a schedule control panel, according to oneillustrated embodiment.

FIG. 54C is a screen print of a task lists control panel, according toone illustrated embodiment.

FIG. 55 is a screen print of an exemplary casino floor display,according to one illustrated embodiment.

FIG. 56 is a schematic diagram of a casino network including corporate,back-office and floor networks, according to one illustrated embodiment.

FIG. 57 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 58 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 59 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 60 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 61 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 62 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 63 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 64 shows a method of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

FIG. 65 illustrates a typical client-server architecture system withmultiple clients requesting information from a server, in which a UDPmulticast notification system enables UDP notification messages to besent reporting that a change has occurred to database table-1 anddatabase table-4.

FIG. 66 illustrates the UDP multicast notification system of FIG. 65being used to send job status updates to BCP clients 2 and “n.”

FIG. 67 illustrates a UDP Broadcast Processor displayed as one componentin the DCM engine.

FIG. 68 illustrates the client registration process in a UDP multicastnotification system.

FIG. 69 illustrates the process of sending a notification message in aUDP multicast notification system.

FIG. 70 illustrates the process of un-registering a client from the UDPmulticast notification system.

DETAILED DESCRIPTION

In the following description, certain specific details are set forth inorder to provide a thorough understanding of various disclosedembodiments. However, one skilled in the relevant art will recognizethat embodiments may be practiced without one or more of these specificdetails, or with other methods, components, materials, and the like. Inother instances, well-known structures associated with computingsystems, networks including servers, routers, bridges, firewalls, andthe like, and gaming devices including electronic gaming machines havenot been shown or described in detail to avoid unnecessarily obscuringdescriptions of the embodiments.

Unless the context requires otherwise, throughout the specification andclaims which follow, the word “comprise” and variations thereof; suchas, “comprises” and “comprising” are to be construed in an open,inclusive sense, which is as “including, but not limited to.” Referencethroughout this specification to “one embodiment” or “an embodiment”means that a particular feature, structure or characteristic describedin connection with the embodiment is included in at least oneembodiment. Thus, the appearances of the phrases “in one embodiment” or“in an embodiment” in various places throughout this specification arenot necessarily all referring to the same embodiment. Furthermore, theparticular features, structures, or characteristics may be combined inany suitable manner in one or more embodiments.

As used in this specification and the appended claims, the singularforms “a,” “an,” and “the” include plural referents unless the contentclearly dictates otherwise. It should also be noted that the term “or”is generally employed in its sense including “and/or” unless the contentclearly dictates otherwise. The headings and Abstract of the Disclosureprovided herein are for convenience only and do not interpret the scopeor meaning of the embodiments.

FIG. 1 shows slot management system 101, according to one illustratedembodiment. One conventional gaming machine management system is the XYZOne System, which is designed to provide essential functionality forgaming facilities. The present example embodiment provides for a unifiedgaming machine management system that offers the full feature sets whichare desirable for a Class III casino floor with a rich gamingenvironment and providing the flexibility to mix Class II and Class IIImachines on the same gaming floor. To accommodate this unification, manyfeatures and functions are needed to provide a robust functionalcapability. In the example embodiment, an architectural framework isprovided that enables the addition of modules and functionality. Slotmanagement system 101 may use standards-based communication protocols,such as HTTP, XML, SOAP, and SSL. Slot management system 101 may be ascaleable system, which may advantageously employ off-the-shelfcomponents, such as conventional servers and storage devices. Slotmanagement system 101 may utilize standard user interfaces for allsystem front ends, such as a display, a keyboard, a mouse, andconventional Windows software. An example front-end may be a managementterminal (server) 103 from which an operator can utilize a userinterface to communicate with player account system server 105 andreview and/or modify player information contained in a player databasemanaged by player account system server 105. Slot management system 101may use standardized authentication, authorization and/or verificationprotocols, which may be implemented and/or controlled by aserver-to-server (S2S) server 107 which enables the secure communicationof data and information between the respective servers within the slotmanagement system 101. Third party interface 109 may further provide forthe incorporation of third party servers and storage devices, such asIGT/Rocket server 111 and Gaming Database 113, using the standardizedauthentication, authorization and verification protocols. Slotmanagement system 101 may support a wide range of promotional tools toenable various promotional and marketing programs which may be used inconjunction with casino market place server 115, such as a CMP, oranother system gaming subsystem. Slot management system 101 includestransaction server 117, for example an iView transaction server thatcommunicates with iView apparatuses which are incorporated with gamingmachines connected to the network, where iView apparatuses include asecondary display connected to a motherboard including a microprocessoror controller, memory, and selected communication, player, and/or gamingsoftware, such as a conventional video wagering game or multi-mediapresentations which may be enabled by a player, the gaming machine, orthe slot management system. It may be appreciated that transactionserver 117 can be designed to drive and communicate with othernetwork-connected apparatuses having a display and user interface. Inthe contemplated embodiments, the networked apparatuses, such as theiView apparatuses, are incorporated with slot management system 101 tomulti-task as both a presentation engine and a game management unit(GMU). To provide flexibility, slot management system 101 utilizes openstandard GSA (Gaming Standards Association) protocols for ease ofintegrating various manufacturers' devices and a windows-based systemfor ease of operators (users) in programming and obtaining data from,and adding data to the system.

FIGS. 2A(1)-2A(2) show operation of a download and configuration serversystem 201, according to one illustrated embodiment.

The download and configuration server system 201 includes controlstation 203, which may include a display and a user interface. Thedownload and configuration server system 201 may also include a downloadand configuration services block 205 (including for example, a downloadserver or Web-accessible service, a download handler server or Webaccessible service, a configuration server or Web-accessible service, anoption configuration server or Web-accessible service, a schedulerserver or Web accessible service and a scheduler server orWeb-accessible service). The download and configuration server system201 may further include a download and configuration database block 207,which may include, for example, conventional storage depositories suchas a download database 227, a schedule database 229, and a configurationdatabase 228. The download and configuration server system 201 mayadditionally include a network components block 209, for example,conventional hardware and software to support IIS 260, MSMQ, and DNS, aSQL report server, an active directory 245, a certificate server, adownload library 234, and an SDDP (Software Download Distribution Point)252. The download and configuration server system 201 may furtherinclude a Game-to-Server (G2S) host block 211, which may, for example,include a download handler 233, an executive service 220, an optionconfiguration handler 232, a G2S engine 280, a delivery agent, and a G2SWeb-accessible service. The download and configuration server system 201may even further include an electronic game machine (EGM) block 213,which may, for example, include a facility floor of network-connectedgaming machines and tables which may each include an iView or similarproduct features and/or a gaming management processor unit which areindividually identifiable and addressable over the network. Thereferenced Web services may utilize a secure HTTP transmission protocolused to communicate with the slot management service and vice-versa. Thesystem 201 may operate using Web protocol and Web services to serveinformation and process transactions, in contrast to serving Web pagesin the traditional sense.

Download and configuration server system 201 enables the transmission ofsoftware files, packages or modules to one or more clients, such asgaming machines or gaming tables, via, for example, a casino networkusing the Gaming Standard Association's (GSA's) Game to System (G2S)message protocols. The configuration portion of server system 201enables the selecting of specific settings and options on one or moreclients using GSA's G2S message protocols, such as to modify the Alphaoperating system on conventionally available gaming machines, or athird-party gaming machine, or table operating systems. The respectivesubsystems of server system 201 communicatively couple to controlstation 203. The control station 203 includes a common user interfaceapplication, such as a control panel (e.g., Bally Control Panel 216 orBCP 216) software application, so that a user can request data and issuecommands for the processing of download and configuration operationsthroughout the network.

Download and configuration server system 201 provides for the followingG2S download class features: 1) the G2S download class provides astandardized protocol to manage the downloaded content on all G2Scompliant gaming machines or tables (i.e., EGMs 213) from all G2Scompliant host systems; 2) the G2S download class enables installationof downloaded packages; 3) the G2S download class enables the removal ofsoftware (uninstall); 4) the G2S download class enables scheduling ofinstallation and/or removal of software including enabling schedulingoptions that relate to a specific time, EGM state, or interaction with ahost server or technician; 5) the G2S message class supports reading aninventory of downloaded packages and installed modules, which providesthe capability to effectively manage the content on the EGM 213; and 6)the G2S message class enables recording transaction logs for packagesand scripts on a transaction database accessible through control station203. This feature provides an audit capability or transaction tracer fordetermining how content came to be on an EGM 213.

The download and configuration server system also provides the followingG2S option configuration (optionConfig) class features which allows forthe selection of various configuration options: a) the optionConfigclass provides a convenient and efficient mechanism to remotelyconfigure EGMs 213; and b) the G2S optionConfig class provides fordownloading options available from within an EGM 213.

The download and Configuration server system 201 implemented G2S classes(optionConfig, download, and scheduler) are also integratable throughsecondary displays, such as the iView, by incorporating, for example, aniView transaction server. Thus, download, configuration, andconfiguration options may be implemented at selected EGMs 213 throughtheir respective Main Processor Unit (MPU) or through iViews. In thecase of using the iViews for network communications, a separateprocessor board is provided along with display and user interfaces.Communication channels are connectable between the iViews and the MPU toenable the download, configuration, and configuration option processes.Some definitions of terms and components follow:

Databases—The databases return information is based on the results of astored procedure call. For example, the following databases, which aredescriptively named, may be utilized: Core; Configuration; Download;Activity; and Schedule.

Control panel 216 (BCP)—As an example, the control panel application,such as a BCP 216, can be client implemented on control station 203encapsulating all the functionality to support the command and controlportions of the download and configuration features of a facility orfacilities. Downloads and configuration options can be remotelyscheduled or deployed immediately by a user through control station 203.Notifications, approvals, searches, and reports produced through serversystem 201 can be viewed by a user through a display or by hardcopyprovided by a printer connected to control station 203.

Control station 203 can be utilized for remote downloading andconfiguration of games and game operating systems of connected EGMs 213.Also, control station 203 can be utilized to download content to or toconfigure the iView (or similar components) and second game displays ormonitors (for instance, in cases in which an EGM 213 has two or moremajor displays) (which may also include an additional processor unitsuch as for example in the case of multiple games operable on a singleEGM 213 on separate displays), as well as peripheral software forcomponents in the games like bill validators and ticket printers.

Control station 203 can be utilized for the throttling of systemresources based on the requested changes. For example, if the userrequests several high bandwidth consuming jobs be initiatedconcurrently, the control station 203 would advise the user that thiswould utilize more than allocated bandwidth and require changes to theproposed schedule. It is also contemplated that the control station 203could recommend changes to the schedule to ease the work requirement forthe user.

Control station 203 can be utilized for the broad-based change to gamingfloors to support special events. For example, on Halloween aspecialized background or theme could be downloaded or configured on allcapable games and devices for the duration of the event. This conceptcan be further extended to enabling specialized bonus games on otherplayer centric activities relating to the special event or holiday. Thisallows a user of control station 203 to fully customize the propertywithout the manual effort required with current systems andtechnologies.

Control station 203 can be utilized to fully view in a graphical fashiongaming floor configurations that have occurred in the past or areproposed for the future. This allows the user of control station 203 toeasily and quickly compare past gaming floor configurations toconfigurations proposed for the future in an easy to understandgraphical manner. It is contemplated that these configurations beanimated in a manner that realistically depicts the activity on thegaming floor over a period of time allowing the user of control station203 to visually assess the impact of the proposed changes.

Control station 203 can be utilized to view machine utilizationinformation over time to determine where certain groups of players spendtheir time while at a property. For example, if certain demographicgroups are inclined to utilize gaming machines configured at $0.25 perplay and this control station 203 capability can illustrate the factthat during certain times of the day this gaming machine configurationis completely utilized and that a large group of this demographic isscheduled to visit the property, the casino manager could opt to enablemore of this type of game so players are not waiting for an opportunityto play. It is contemplated that this feature is presented in ananimated fashion such that the user of control station 203 may select adate range and analyze in real-time, game usage by time of day and byplayer demographic. This feature also requires control station 203 haveaccess to, and the capability of processing, information from the playermarketing system, or have access to a data stream feeding the playermarketing system.

Control station 203 has the capability to allow groups of gamingmachines to be identified and operated via a number of query options.This aids the user in quickly and effectively finding the gamingmachines to apply changes. It is contemplated that advanced selectioncriteria, such as performance over the last 30 days, be considered as aquery parameter. The control station 203 can provide the capability toutilize a graphical representation of the gaming floor. This allowsselected groups of games to be graphically represented on a floor map aswell as in a list form.

Control station 203 can utilize historical slot game performance data toprovide guidance for new floor configuration options. The historicaldata may be accessed in the download system data stores or from anexternal business intelligence system. It is contemplated that thecontrol station 203 may be programmed to allow for automated floorconfiguration changes based on the historical performance data. Thiscapability may be applied automatically or via an interface requiringonly approval from the user prior to applying the changes.

Database Web Services—These are World-Wide Web (Web) services that areconventionally available to be re-used by other user interfaces andservice applications connected to slot management system 101. In otherwords, this is a secure, closed, system network using Web servicesconnected on demand with the slot management system 101 (FIG. 1).

Handlers—These are the logic libraries that are responsible forexecuting the business logic of the system.

Network Components—The following list of network components, or portionsthereof, may be implemented and/or required by the download andconfiguration server system 201: Certificate Server; DNS; DHCP,Application Firewalls, Hardware Firewalls, Network Load Balancers.

Third Party Software Applications—the following list of 3^(rd) partyapplications my be utilized or required by the server system 201: IIS260, MSMQ, SQL Server, SQL Server Reporting Services, Active Directory245, Microsoft Windows 2003 Server.

G2S Engine 280—This service will receive G2S messages directly from EGMs213 and dispatch them to the respective subsystem of server system 201based on the message component type.

EGMs 213—Electronic Gaming Machines, which may include gaming tableswith processor and/or display components.

iView—For example, a conventional apparatus providing a player oremployee user interface and display at EGMs 213 connected to the networkincluding the player tracking server and enabling a player or employeeto request and receive information, to receive award notifications, totransfer credits, and to conduct such activities through the apparatusas is enabled on slot management system 101. One usage of an iView-typeapparatus may be to display marketing and player tracking informationand various shows on the occurrence of an award or win by a player. Suchapparatuses may also allow gaming, such as with server-based games oreven independent games stored on their respective processor boards.Thus, separate games may be implemented through the iView-type device,apart from the main game of EGM 213 controlled by the MPU. In turn, thecontent of the iView may be separately modified as through downloads orconfigurations or configuration options.

Control station 203 is able to retrieve from the database and view alllogin attempts to the server both successful and failed. A user may belocked out of access to the control panel application at control station203 after too many failed login attempts. The recorded transaction logmay include the login ID, data, time of login and duration.

The Web services may support functionality between control station 203and database block 207. The Web services may also support unsolicitedmessages between the G2S handlers and control station 203.

Server system 201 may maintain a record or transaction log of loginattempts to the server both successful and failed. The log may includethe login ID, data, time of login and duration. Server system 201 mayalso maintain a transaction record or log of all events and activityoccurring on server system 201. The log may include a record of whichlogin session and when the event occurred.

Server system 201 may also maintain a log of communication events withany EGM 213. Server system 201 may also maintain the status of each EGM213 including: game history data; download status (available, requested,downloading, applied, and rejected); package information (available forinstall, requested, being downloaded, downloaded, installed); hardwareinformation; software module information; and/or error conditions.

The configuration and download server system 201 may dynamically buildpackages to be downloaded based on EGM 213 inventory and availableupdates, fixes and new data for EGMs 213. The configuration and downloadserver system 201 may verify requests from EGM 213 including whether ornot the EGM 213 is valid and is in a functional or operational state tomake the request. All requests may be logged and contain the requestingEGM 213 identifier, time and date, specific request, and EGM 213operational status. The configuration and download server system 201 maycommunicate with Software Distribution Point servers (SDDP) 252 tomaintain a list of packages that are available for supported EGMs 213.The configuration and download server system 201 may supply the locationof the SDDP 252 when instructing an EGM 213 to add a package. Theconfiguration and download server system 201 may verify that allrequired hardware and software for a package to be sent to an EGM 213exists before instructing EGM 213 to retrieve the package. Theconfiguration and download server system 201 may support multiple EGMs213 in multiple sites and/or facilities and EGMs 213 produced bymultiple manufacturers. The configuration and download server system 201may verify that a software package can be installed on a selected EGM213 before instructing EGM 213 to add a package. Such verification may,for example, use information in the package header and informationstored about selected EGM 213. The configuration and download serversystem 201 may be able to track which packages are installed on anygiven EGM 213 and verify the data by requesting a selected EGM 213 tosend package install information. The configuration and download serversystem 201 may report bad images and errors and log them when failedpackage installation information is received from an EGM 213. Theconfiguration and download server system 201 and SDDP 252 may be used tocontrol all network pacing, bandwidth, error recovery, and monitoring.The configuration and download server system 201 may be used to maintainthe location of all SDDP 252 and the packages available on each.

The Software Download Distribution Point (SDDP 252) server may beutilized to maintain all downloaded software packages in a securelibrary with the required number of secure backups defined by ajurisdiction. The SDDP server 252 may be used to restrict access to thelibrary that stores all software download packages to only authorizedpersonnel. The access may limit access, such as to only allow writeaccess to those authorized to add, delete, and update packages and readaccess for all others authorized to access the library. The SDDP server252 may provide secure software level firewalls to restrict access toeverything saved on the server. The SDDP server 252 may maintain a logof login attempts to the server both successful and failed. The log mayinclude the login ID of a user, data, time of login and duration. TheSDDP server 252 may maintain a log of all events and activity occurringon server system 201. The log may include which login session and whenan event occurred.

Software packages added to the software library may be verified from thepackage data using an MD5 or SHA1 hashing algorithm to validate the dataor some other verification tool. The verification string may be added toa package header and used to re-verify the package when it is downloadedto the EGM 213.

All verification failures and related errors may be logged, and the logentry may contain the date and time, the ID of the person running theprocess at the time, and the specific type of error that occurred. Theymay also be displayed on the correct display area.

The SDDP server 252 may be utilized to provide selected EGMs 213 withthe communications port location and IP address used for sendingsoftware package data to the EGM 213. All data within a download packagemay be compressed using conventional compression techniques andtransmitted in compressed format. On receipt, EGM 213 may decompress thedownloaded software package.

FIG. 2B shows a tiered-layer architecture of a download andconfiguration system, according to one illustrated embodiment.

A presentation layer 214 may include the control panel application 216.The control panel application 216 is loaded on control station 203(FIGS. 2A(1)-2A(2)) which provides a user interface and display throughwhich the download and configuration portion of the slot managementsystem 101 (FIG. 1) is managed.

A business logic layer 218 may include G2S Host 219, which may includeG2S engine 280 components. G2S Host 219 may be used to send and receiveG2S protocol messages to and from EGMs 213 and other configurabledevices. G2S Host 219 may also be used for the packaging and unpackagingof the internal system messages and G2S protocol messages. The businesslogic layer 218 may also comprise Download and Configuration logiclibraries, Executive Service 220, and the Scheduler Service 221 whichare responsible for implementing the Business Logic of the system.

A data access layer 222 may be comprised of Web Services 223, which maybe used to enable methods and/or processes for interacting with a datalayer 224. A network services layer 225 provides network services 226.

The data layer 224 may comprise various databases, for example adownload database 227, configuration database 228, schedule database229, activity database 230, and core database 231, as may be useful forstoring download and configuration system data.

EGM layer 212 may comprise the EGMs 213 and other configurablecomponents like iViews and game controllers.

FIGS. 2C(1) and 2C(2) show a componentization of a download andconfiguration system, according to one illustrated embodiment.

The presentation layer includes the control panel application 216. Thecontrol panel application 216 may be loaded on control station 203,which may include a user interface and display for the user to managethe download and configuration server system 201.

The business logic layer includes Download Service and Logging. TheLogging library may be used to store job logs and may include storingerror and debug logs.

The scheduler 221 may implement the shared base classes for assignmentsand jobs, maintain the job queues, and/or provide execution contexts forhost-originated activities. The scheduler 221 may also include upkeep(e.g., flush) of an outdated job and job log entries.

G2S Host core 219 may provide the mechanisms to separate protocolspecifics from application logic. G2S Host core may receive informationfrom the application libraries (e.g., Configuration), and may beutilized to implement the interfaces that the application and protocolcomponents require to fulfil their needs.

An option configuration handler 232 may be utilized to implement the G2Sclass's specific to the Option Configuration context.

A download handler 233 may be utilized to implement the G2S class'sspecific to the download context.

A download library 234 may be part of the library of software packagesavailable for download to EGM's 213.

The SDDP 252 may be comprised of a Website responsible for downloadingsoftware packages to EGMs 213.

The data access layer 222 may connect Web-based structure and serviceswith the download database 227. The data access logic required for thedownload and configuration system 201 to interact with the downloaddatabase 227 may be contained within the download Web service 236 (FIG.2B). The download Web service 236 may also provide structure andservices for communicating download commands, such as between the BCP216 and a download handler 237 via the executive component 220 (e.g.,via an executive Web service 240).

A configuration Web service 238 (FIG. 2B) may provide Web-basedstructure and services allowing the interaction with the configurationdatabase 228. The data access logic required for the download andconfiguration system 201 to interact with the configuration database 228may be contained within the configuration Web service 238. Theconfiguration Web service 238 may also provide Web-based structure andservice for communicating configuration commands, such as between theBCP 216 and a configuration handler 239 via the executive component 220(e.g., via the executive Web service 240).

A scheduler Web service 241 (FIG. 2B) may provide Web-based structureand services to consuming components to allow the interaction with theschedule database 229. The data access logic required for theconfiguration and download system 201 to interact with the scheduledatabase 229 may be contained within the scheduler Web service 241.

A core Web service 242 may provide Web-based structure and services toconsuming components to allow the interaction with the core database231. The data access logic required for the system to interact with thecore database 231 may be contained within the core Web service 242.

An activity Web service 243 may provide Web-based structure and servicesto consuming components to allow the interaction with the activitydatabase 230. The data access logic required for the system to interactwith the activity database 230 may be contained within the activity Webservice 243.

A security Web service 244 may provide Web-based structure and servicesto consuming components to allow the interaction with active directory245 for security purposes (e.g., authentication, verification,encryption, and the like). The security Web service 244 may be used as aWeb-based interface for retrieving and storing security data in theactive directory 245 or other directories, databases or other securityrepositories.

At the data layer 224, the configuration schema may implement theconfiguration database 228; download schema may implement the downloaddatabase 227; activity schema may implement the logging database 230;core schema may implement the translator or core 231 database; andschedule schema may implement the schedule database 229.

FIGS. 2D and 2E show a download and configuration server 15 systemnetwork according to one illustrated embodiment.

Download and configuration server network 201 is a portion of slotmanagement system 101, which provides a suite of subsystems designed toprovide customizable solutions by allowing users to select productswithin the suite to meet their needs for particular facilities, such asa casino manager seeking to manage single or multiple properties.Download and Configuration (Download and Config) are two of thesubsystems offered in the suite that provides a user, such as the SlotOperations staff, an efficient mechanism to remotely configureelectronic gaming machine (EGM) 213.

The Download and Config Software utilized together with the apparatusesas shown in the figures may be used to enable a casino Slot Operationsstaff to schedule and change a game(s) on the casino floor from akeyboard.

Using the Control Panel (BCP) interface 203, the staff may be able toschedule, configure, download and activate changes to games on thefloor, without touching an EGM 213 on the floor. The Download and Configsoftware application may be loaded on control station 203 to enable thesending of information over the casino network using G2S & HTTPSstandardized message protocols that manage the downloaded content. Fromcontrol station 203, a user, such as casino staff, can change cabinet orgame options, or games in EGMs 213. There are numerous selections thatthe staff can schedule to configure or make a minor change. Someexamples of the types of software that may be downloaded or optionswhich may be re-configured are:

Cabinet Options Game Options Download Options Sound Game/Theme Change agame, theme, &/or Reel spin speed Paytable paytable Background colorDenomination Change game operating system Attract mode

In order to implement the download and configuration features, oneapproach is to install slot management system 101 at a facility, suchas, for example, the Live slot management system 101. The implementationof the download and configuration features further contemplates theimplementation of server hardware and related equipment as shown in thefigures, and particularly FIGS. 2A(1)-2E, including software to performthe needed functions for communicating relevant data and instructions,the implementation of download ready EGMs 213, such as EGMs 213 with anAlpha operating system with remote download and configurationcapability. An example system for implementing the download andconfiguration network 201 may be a XYZ One System together with the LiveFloor program. Another example implementation of the Download andConfiguration server network 201 may be in conjunction with other slotmanagement systems incorporating the Live Core program.

An example process for using the download and configuration server 25network 201 is as follows: A casino operator decides to change gamethemes on the Alpha V20D-20 EGMs 247. The software game themes arelocated on the SDDP Server 252. The Download management tools arelocated on the Application/Database Server System 251. One or moreservers separate from the SDDP Server 252 contain the game themesoftware, such as for security or redundancy purposes. The Alpha EGMs247 are identified on the casino floor using the BCP 216. A Downloadmanagement tool, such as the BCP scheduler may be used through a menu toidentify: the date and time to download the game packages; the gamepackages to send to the specific EGMs 213; the date and time toautomatically activate the games on the EGMs 213 after the download. Atthe selected date and time, the EGM 213 may open communication with theDownload Database 227. The EGM 213 requests software from the SDDPserver 252. The SDDP server 252 downloads the specified game informationto the EGM 213 using a secure transmission protocol such as HTTPS. Thedownload to the EGM 213 may occur in the background operation of theAlpha OS, so that game play is not interfered. The EGM 213 mayde-activate game operation for a predetermined amount of time subsequentto the last play on the EGM 213, such as five minutes, and issue amessage on one of its display panels that it is temporarily offline, andat which point the EGM 213 can initiate installation of the downloadedsoftware. A record of the transmissions and corresponding activity ofthe EGM 213 is relayed to a retrievable storage on the network, suchthat a privileged user may operate the BCP 216 to run the reportsidentifying the old and new games, the date changed, and by whom. Userprivileges may be restricted as discussed previously to provideadditional levels of security and flexibility within the system and forthe casino operator or users of slot management system 101 and downloadand configuration server network 201.

Example download and configuration components that are shown in FIGS. 2Dand 2E indicate a system that supports up to 10 EGMs 213 through asingle Cisco 2950 switch. As the number of EGMs 213 increase, the typeand/or number of servers, switches, firewalls, and pipelines may bechanged to accommodate higher traffic volumes and improve or avoiddegradation of performance. In an example embodiment, the followingapparatuses and software are incorporated. An SDDP server 252, whichincludes a download software library. The SDDP server 252 executes gameserver software, and the download software library stores download gamesoftware.

An application/database server 227 includes core databases, and providescore services as well as download services. The core databases mayinclude a core database, a meter database and an activity database. Thecore services may include: communications, initiation and validation,certificate, IIS, MSMQ, DNS, DHCP, and active directory services. Thecore services may also include: meter services, activity services,cabinet services, and game play services. The download services mayinclude certificate, IIS, MSMQ, DNS, DHCP, and active directoryservices. The download services may further include: a Web service, aconfiguration Web service, a scheduler Web service, a download handlerWeb service, an option configuration handler Web service and a schedulerservice.

A G2S may include certificate, IIS, MSMQ, DNS, DHCP, and active 20directory services. The G2S may also include a SQL Report, Web Service,and delivery agent. Download and configuration databases may include: adownload database, a configuration database and a scheduler database.

An adaptive security appliance (ASA) may create a firewall betweenback-end and floor systems. Such may provide a proactive threat defensethat stops attacks before they spread through the network, controlsnetwork activity and application traffic, and delivers flexible VPNconnectivity.

Example Example Components Example Hardware Software SDDP server 252(SDDP 252 Pentium IV 2 GB RAM OS - Microsoft may be placed on its own100 GB SATA 2 Windows 2003 server to comply with some NIC cardsMicrosoft SQL jurisdiction requirements.) 2005 Application LibraryServer Pentium IV 2 GB RAM OS - Microsoft 100 GB SATA 2 NIC Windows 2003cards Microsoft SQL 2005 Databases • Scheduler Pentium IV 2 GB RAM OS -Microsoft Download • Configuration 100 GB SATA 2 NIC Windows 2003 cardsMicrosoft SQL 2005 Networking Cisco 2950 Switch, 24-port Cisco ASA 5510(firewall) Connecting wiring between CAT-5 cables 15 feet devices long 2cables per EGM 213

FIG. 3 shows an exemplary download and configuration user-based treelogic flow diagram, according to one illustrated embodiment. Theexemplary users shown in the diagram have the following descriptivenames: Reviewer, Approver, Editor, Casino Manager, and Casino Analyst.The Reviewer is a user who can view tasks that are only related to view;this user does not have the right to change anything in the system. Theresponsibility of the Approver is to approve the tasks that need to beapproved by an additional user. The Editor has the right to edit, view,set and cancel tasks. The Casino Manager is a user who may or may not bedirectly involved with day-to-day management of gaming terminals,approves changes to configuration, and views gaming performance data.The Casino Analyst (i.e., performance analyst) may generally reportdirectly to the Casino Manager and may be tasked with analyzing thefinancial performance of the casino, including the network of electronicgaming machines. After analysis, the Casino Analyst may produce a listof recommendations to the Casino Manager designed to optimize theelectronic gaming network performance.

The following devices and systems may be included within the describedslot management network system and may have the referenced capabilities:

EGM—G2S Protocol: An Electronic Gaming Machine (EGM) 213 that implementsthe Game To System (G2S) protocol for download and configuration.

iView—G2S Protocol: Device for player touch point services. It may beused to display marketing and player tracking information. It may beincorporated within the network to provide gaming independent of orincorporated with an EGM 213. It has a separate network connection asindicated in the prior figures.

3rd Party Server: Third party server that provides download andconfiguration management of non-G2S EGM 213 devices. The Control Panel(BCP) 216 may use an extension of System to System (S2S) protocol tomanage download and configuration of proprietary EGMs 213 through theproprietary (3rd party) server.

Slot Management System: Central system responsible for accounting,vouchering, player tracking, and the like (e.g., Slot Data System).

FIG. 4 shows an exemplary download tree-logic flow diagram for managinga software package library with the SDDP 252, according to oneillustrated embodiment. In the illustrated example:

Install Package—A package is a transport container designed to deliverone or more modules to a downloadable device (like an EGM 213, iView orGC hereafter referred to as EGM 213). This use case allows users toinstall packages to the SDDP 252. This may include three primaryfunctions. 1) copy the package files themselves from the CD to thecorrect directories on the SDDP 252; 2) update the SDDP 252 inventorytables in the download database 227; and 3) log all of this activity.

Uninstall Package—Removes the package from the SDDP 252, updates thedownload database 227 inventory and logs the activity.

View Packages—This use case allows the users to examine the packagesthat exist at the SDDP 252.

View Package Modules—This use case indicates that users may view themodules contained in a package.

View Package Management Logs—All activities like installing anduninstalling of packages are logged by the system; this use case denotesthe user's ability to review these logs.

Verify Packages—Checks the hash values and certificates of the packagesin the SDDP 252 directories to confirm no tampering has occurred.Confirms that no unauthorized packages exist on the SDDP 252.

FIG. 5 shows an exemplary download management tree logic flow diagram,according to one illustrated embodiment:

Create Download Assignment—Create an assignment of packages(s) to acollection. A new assignment is inactive and has a default schedule ofnow, an empty collection, and contains no packages.

Edit Download Assignment—Described in detail below with regard to FIG.6. This includes managing the collection membership, what is assignedfor download, whether the assignment is active, and its schedule.

Download Views—Described in detail below with regard to FIG. 8. Userscan examine current EGM 213 inventory, the package library (viapackages, or via modules), pending jobs (scheduled, active assignments),running jobs (changes in progress), and completed jobs.

Initiate Package Installation—When a package has been distributed to oneor more EGMs 213, the EGM 213 escrows the package, verifies it is whatit is professed to be, and awaits an “initiating event.” What that meansvaries by jurisdiction; it may be an attendant action at the EGM 213, atthe system, or allowed to occur automatically. This use case covers theconcept that a BCP user may manually initiate a package installation, orit may be automated at the system level.

Purge—This refers to the function of purging old assignments from thedatabase. Assignments are marked deleted and may become invisible to theuser interface (UI) tools. Deleted assignments may be purged if theywere never active.

Approve Assignment—This use case shows that an assignment may beapproved by an Approver. This is a user with an approval role in thesystem.

FIG. 6 shows an exemplary flow diagram for editing download assignments,according to one illustrated embodiment.

Manage Collection—A collection may be used by more than one assignment.The user can modify the membership of the collection.

Add and remove EGMs 213. Dynamic collection may be allowed. These arebased on matching some criteria such as, for example, all EGMs 213playing nickel poker.

In the case of dynamic collections, change how a dynamic collection'smembers are determined and convert a dynamic collection to a static one.

Managing a collection is described in more detail below with regard toFIG. 7.

Set Collections—Choose which EGMs 213, directly or via other collectionsthat this assignment will affect.

Add or Remove Package—The user can pick from available packages and addthem to the assignment for download. The modules included withinpackages are also displayed for reference.

Edit Download Schedule—The user can edit scheduling options fordownload.

The user can schedule a start date for download using the BCP 216. Itmay be noted that the start date indicates the date the download processbegins. It may take an indeterminate amount of time for the downloadedpackage to be ready to be installed on a given EGM 213. This is the casewhere download occurs in a facility that is operating. If the facilityis shutdown at a selected point in time or if it is not yet operational,download may occur as rapidly as the throughput pipelines and bandwidthof the servers and routers will allow on the system. Also, according toone embodiment, to avoid download conflict when multiple downloadassignments exist for the same module type on an EGM 213, the assignmentwith the latest creation date may take precedence.

Edit Install Schedule—The user can edit scheduling options to installpackages.

Edit Assignment Attributes—The user can edit the name and description ofan assignment. According to one embodiment, one of the most importantattributes is active. Assignments can be created, edited, scheduled, andsaved without having them take effect. For an assignment to be scheduledand affect the collection, it must be made active. The user may alsode-activate an assignment.

FIG. 7 shows an exemplary download and configuration flow diagram formanaging a collection, according to one illustrated embodiment.

Create—Create an empty EGM collection. A collection is a list of EGMs213. A collection may also include other collections. On the BCP 216user interface and display, these may be referred to as EGM groups.

Delete—Remove EGMs 213 or EGM collection from a collection.

Edit—Add or remove EGMs 213 or EGM collection from a collection

Duplicate—Make a copy of an existing collection and give it a new name.

View—View EGMs 213 or EGM collection.

Purge—Remove a deleted collection from the Database if it isunreferenced.

FIG. 8 shows an exemplary flow diagram of download views, according toone illustrated embodiment.

View EGM Inventory—The user may select any EGM within the currentlyselected download assignment, and see the EGM module 213, component, andpackage inventory.

Refresh Inventory—Force an obtain inventory job to run on the EGM 213and update the BCP 216 to display the newest data. Additionally and/oralternatively the refresh inventory may report on differences detected.Normally, the DB inventory may be expected to substantially match theactual EGM inventory.

View Available Modules—The download system maintains a library ofpackages, which deliver (i.e., install or un-install) modules. The usercan browse which packages are available for download. According to someembodiments, only the package(s) that are compatible with the referencedEGMs 213 are shown. In other embodiments, other choices may bepermitted, like packages compatible with the reference EGM in acollection.

View Available Packages—The download system maintains a library ofpackages, which deliver (install or un-install) modules. The user canbrowse which packages are available (in the library) for download. Theborne module(s) are displayed in association with each availablepackage, including any module or [hardware] component that the packagedepends on for its installation to succeed.

View Download Jobs Status—This use case allows the users to view thecurrent status of download jobs. The download jobs may have differentstatus such as, for example, Pending, Running or Completed. Individualpackage downloads may, for example, have states as defined by the G2Sprotocol that are sub-states of the pending jobs. The individual packagedownloads may include, for example:

Pending Download Jobs: The host maintains a job queue of upcomingdownload jobs, based on the schedule (e.g., an active downloadassignment scheduled to run in the future will have a pending job).

Running Download Jobs: The host monitors download jobs that are inprogress. This allows the user to examine which jobs are currentlyrunning, their status, and any log entries against that job. It is notedthat each assignment-level job may have one or more EGM-level jobs. Theuser interface displays such relationships by nesting EGM-level jobsunder each assignment-level job.

Completed Download Jobs: Once a job has completed, the job and its logentries may be archived for 180 days. The user can examine the historyof completed jobs for an assignment. Similar to running jobs, eachassignment-level job may have one or more EGM-level jobs. The userinterface may display such relationship by nesting EGM-level jobs undereach assignment-level job.

Cancel Jobs—Informs the host system via the BCP 216 to abort an existingjob. Any new commands for the jobs are not run. An attempt may be madeto send cancel commands to the EGM 213 if appropriate.

FIG. 9 shows an exemplary flow diagram for managing configurations,according to one illustrated embodiment.

Create Configuration Assignment—A configuration assignment supports thedefinition and scheduling of EGM configuration changes. This use caseidentifies different ways for the user to create new configurationassignments.

Edit Configuration Assignment—Once created, the configuration assignmentprovides powerful and flexible means to manage the configuration of EGMcollections over time. The configuration assignment is described in moredetail below with regard to FIG. 10.

Configuration Views—Users may examine current EGM settings, pending jobs(e.g., scheduled, active assignments), running jobs (e.g., changes inprogress), and completed jobs. Configuration views are described belowin more detail with regards to FIG. 11.

Purge—This refers to the function of purging old assignments from thedatabase. Assignments may be marked as deleted and become invisible tothe UI tools.

Approve. Assignment—This use case shows that an assignment is approvedby an approver.

FIG. 10 shows an exemplary flow diagram for editing configurationassignments, according to one illustrated embodiment.

Manage Collection—As described in detail above with regards to FIG. 7, acollection may be used by more than one assignment.

Set Collection—Specify the collection to be used for an assignment.

Edit EGM Options—The user may select one or more option groups for theassignment to affect and edit the options within each selected group.EGM options are described with reference to FIG. 14.

Define Game Play Devices—User may create, delete, or modify the gameplay device that is available on the EGM 213. A game play device isdefined as a game theme and pay table with one or more denominations.For example, Alpha OS EGMs may support up to 100 game play devices. Eachmay have additional options which can be configured directly at the EGM213 or remotely through the BCP 216 once the Game Play Device is definedon the EGM 25 213.

Edit Game Play Device Options—The user may select one or more gamedevices to be activated by the assignment, and edit the options withineach device activated by the assignment.

Validate Assignment—Using configuration assignments may provide a fullyautomated slot floor reconfiguration such as, for example, defining adefault configuration, then overriding it for weekends or a holiday.Such may be accomplished by layering or stacking assignments, which maybe conflicting. The ‘validate assignment’ operation performs a conflictanalysis that reports on such conflicts and may be reportable in thecase of a conflict, such as at the BCP 216. It is noted that by allowingdynamic collections or non-permanent collections a point-in-timeanalysis is provided.

Edit Assignment Schedule—Configuration assignment scheduling mayadvantageously be flexible. In one embodiment the configurationassignment scheduling may be restricted as download assignments are.Scheduling may be understood in terms of how the host arrives on properEGM settings at a given moment in time. Configuration assignments may berun in order of schedule type such as, for example, Permanent, Permanentwith start date, Re-occurring Override and One Time Override. Within theschedule types, the one with the earlier start date goes first. Withinmatching start dates, assignments with static collections run beforedynamic. If the assignments have matching start dates also have matchingcollection types, the assignments with earlier create dates run first.It is noted that in some embodiments configuration assignments ofpermanent and permanent with the start date may include staticcollections.

Edit Assignment Attributes—Names and description are editable. Accordingto one embodiment, an important attribute is Active. The user cancreate, edit, schedule, and save assignments without having it takeeffect. For an assignment to be scheduled and affect the collection, theassignment is made active. The user may also de-activate an assignment.

FIG. 11 shows an exemplary flow diagram of configuration views,according to one illustrated embodiment.

View EGM Options—Within the configuration context, the user may selectany EGM in the currently selected assignment, and view the currentsettings for that EGM.

View Game Play Device Options—View the options which have been set foreach individual game play device on an EGM.

Refresh Options—From the BCP 216, a user may instruct the host tore-obtain the configuration options from an EGM. These are compared tothe current settings and differences may be noted. Normally, the hostmay have an exact copy in its DB as changes are to be reported to thehost according to GSA G2S.

View Configuration Jobs Status—This use case allows the users to viewthe current status of configuration jobs. The configuration jobs canhave a different status like Pending, Running or Completed. Pending jobswill have a sub-status of the configuration set itself as defined by theG2S protocol.

Pending Configuration Jobs—The host maintains a job queue of upcomingconfiguration jobs, based on the schedule. For example, an active,recurring assignment may have a job pending, scheduled for the nextoccurrence. When that job runs, a new pending job is created for thatassignment.

Running Configuration Jobs—The host monitors configuration jobs that arein progress. This allows the user to examine which jobs are currentlyrunning, their status, and any log entries against that job. Note thateach assignment-level job may have one or more EGM-level jobs. The userinterface is operable to display this relationship by nesting EGM-leveljobs under each assignment-level job.

Completed Configuration Jobs—Once a job has been completed, the job andits log entries may be archived for 180 days. The user can examine thehistory of completed jobs for an assignment. Similar to running jobs,each assignment-level job may have one or more EGM-level jobs. The userinterface may display this relationship by nesting EGM-level jobs undereach assignment-level job.

Cancel Jobs—A user may cancel pending jobs and, in response, the systemmay discontinue the pending jobs if they are in progress. If possible,the system will also send the cancel command for each open configurationset.

Clear Override—An optional item is considered overridden if it has beenchanged via the machine's touch screen menus. In this case the hostreceives an unsolicited optionList to report the changes. The host willrespect these overridden settings, even if a subsequent assignment wouldmodify them, until such time as the user clears the override via thisfunction.

View Configuration Assignment—A user may view, but not modify, theconfiguration assignment. This may be a read only version of thecomplete wizard, or it may be just a view of the review page of thewizard.

FIG. 12 shows an exemplary flow diagram for managing reports, accordingto one illustrated embodiment.

View Report—This use case may be used to view reports from the Reportuser interface.

Print Report—This use case may be used to print reports from Report userinterface.

Export Report—This use case may be used to export reports via the Reportuser interface.

FIG. 13 shows an exemplary flow diagram for communicating (interacting)with EGMs 213, according to one illustrated embodiment.

Handle New Connection—When a G2S EGM first comes up, it will connect toa host address set manually at the EGM 213 or discovered via DNS orLDAP. This use case addresses the initial configuration activities thattake place when the host accepts a new connection. For download andconfiguration, each handler listens for the commsStatus event andproceeds from there. By the time commsStatus says open, the initialhandshake with the rest of the floor system may be completed and the EGM213 may exist in the core database 231.

Obtain Configuration—Each EGM reports its current configurationsettings, and reports the options it supports along with the range ofvalid settings for each option.

Obtain Inventory—EGMs 213 may report hardware and software inventory tothe system.

Execute Configuration Jobs—Such is described in detail 10 below withreference to FIG. 14.

Execute Download Jobs—Such is described in detail below with referenceto FIG. 15.

FIG. 14 shows an exemplary flow diagram for executing configuration jobs(assignments), according to one illustrated is shown:

Set Game Play Device—Send the sequence of commands used to define gameson the EGM 213 as defined by the configuration assignment.

Set Configuration Change—Send the sequence of commands used to setoptions for all devices except game play devices as defined by theconfiguration assignment.

Set Game Play device options—Send the sequence of commands to setoptions for all game play devices as defined by the configurationassignment.

Unsolicited Option List—Handle an unsolicited OptionList command from anEGM. This command may cause the setting of EGM overrides in theconfiguration database 228.

Unsolicited Option Change—Handle an unsolicited Option Change commandfrom an EGM. This may be logged as a warning.

Cancel Option Change—When reviewing job status, a user may choose tocancel any job that has not completed. The host may send the requiredcommands to the EGM 213 to cancel this job. If the job completes beforethis happens, the cancel may fail.

FIG. 15 shows an exemplary flow diagram for executing download jobs(assignments), according to one illustrated embodiment.

Download Package—Carry out the sequence of commands required to move thepackage from the SDDP 252 to the EGM 213 escrow area.

Install Package—When a package has been downloaded to one or moredevices, the device escrows the package, verifies it is what it isprofessed to be, and awaits an “initiating event.” In some embodiments,the initiating event may be an attendant action at the EGM 213, at thesystem, or allowed to occur automatically. This use case covers theconcept that a BCP user may manually initiate a package installation, orit may be automated at the system level to carry out the sequence ofcommand required to install the package on the EGM 213.

Cancel Download Jobs—When reviewing job status, a user may choose tocancel any job that has not completed. The host may send the requiredcommands to the EGM 213 to cancel this job. If the job completes beforethis happens the cancel will fail. Some EGMs 213 may not supportcancelling a download in midstream. If so, they will report this error,and it will be displayed in the job status for the cancel job.

FIG. 16 shows an exemplary flow diagram for handling configuration jobs(assignments), according to one illustrated embodiment.

FIG. 17 shops an exemplary flow diagram for handling download packages,according to one illustrated embodiment.

FIG. 18 shows an exemplary block diagram of a control panel 216componentization, according to one illustrated embodiment. In oneembodiment, the Control panel 216 (BCP) is a Window's forms Smart Clientapplication that operates on control station 203 which may, for example,be a Pentium PC with a Microsoft Windows operating system or aLinux-based operating system with Windows. The BCP 216 Application mayencapsulate all the functionality to support the command and controlportions of the download and configuration features of the project. TheBCP 216 provides operators with an interface to remotely specify andcontrol download and configuration functions for the EGM 213 or devicesacting as EGMs 213 such as, for example, an IView or Game Controller.The BCP 216 also provides regulators and managers with the ability toreview and approve these functions. The BCP 216 combines the functionsof Download and Configuration into one application since they may betightly linked, and the metaphors or concepts used to make them visibleto users may be substantially the same. Some terms associated withDownload and Configuration are Named Collections, Assignments, Jobs,Manual Overrides, Notifications, Packages, Device Classes, and Game.Play Devices, Option Groups, and Option Items:

Named Collection: A set of EGMs 213 can be treated as or operated on asa group in a manner similar to an Email Group.

Assignment: A set of download or configuration instructions groupedtogether as a “document” that can be saved, recalled, and reused. Commonto Download and Configuration assignments are a name, description, and agroup of EGMs 213 to which the assignment will apply. A schedule may beattached to any assignment as well.

Download Assignment: An assignment that lists the packages that shouldbe downloaded to the EGMs 213 in the assignment's collection as well asthe installation rules to use.

Configuration Assignment: An assignment that lists the configurationoptions to be set on the EGMs 213 in the assignment's collectionincludes option items in option groups for ordinary device classes aswell as G2S_gameplay device option groups.

Job: Encapsulation of the data and commands used to carry out anassignment. An assignment job will normally be split into EGM jobs foreach EGM referenced by the assignment.

Manual Overrides: If an operator opens the game cabinet and setsconfiguration options via the menus, these options are consideredoverridden by the EGM 213 and may retain their settings unless theoverride is explicitly cleared via an interface in the BCP 216.

Notifications: Any tasks or results that must be displayed to the user.In some embodiments, notifications require action of some sort such as,for example, approval. In other embodiments, notifications can simply beacknowledged. For example, if a download is saved and ready to run, itmay first require regulator approval. The regulator can look in thenotifications list, examine this entry, and approve or deny it.

Package: A structured file containing header information and thedownloadable payload. This payload could be a Game OS, Game Theme,Removal Scripts, or any set of modules defined by the manufacturer.Packages are stored on the Software Download Distribution Point (SDDP252)

Device Class: One of the predefined G2S device classes such asG2S_cabinet or G2S_gamePlay.

Game Play Device: A type of Device Class representing a game bundle orcombination that is ultimately selectable by a player on the EGM 213. AGame Play device specifies a particular theme, pay table anddenomination list.

Option Group: Each device class may have many option items which arearranged into named option groups.

Option Item: The root level configurable item. Option items are definedto have among other things an ID, name, type, value, default value,minimum and maximum values. Option items may also include a list ofvalues. For example, “car_color” might have the values “red” and “gold.”One embodiment of the user interface is modeled after many commonWindows applications with dockable panes to show items one can navigateon or to display options. Another embodiment of the user interfaceincludes a document area much like Visual Studio for displaying thingslike assignments that can be saved. The main windows or pains are listedin the composition section below.

The BCP 216 is a smart client application that may depend on the Dot Net2.0 or similar framework. It may be deployed via the Systems Web site.Any software dependencies may be automatically downloaded with theapplication. The BCP 216 may run on Windows 2000 or newer OS machines.In one embodiment, as illustrated in FIG. 18, the BCP 216 communicateswith the rest of the download and configuration network system solelythrough Web Services 223. The BCP 216 may, for example, utilize the DotNet 2.0, Infragistics 5.3, and various conventional utility DLLs. Thesemay be automatically downloaded and installed as part of an initialdeployment on control station 201. In order to operate with theWeb-based services, control station 201 may be connected to the Web, andthe BCP 216 application may be able to reach the Web server running saidWeb-based services. A user with proper credentials may be required tolog in. Also, the workstation (control station 201) upon which the BCP216 application is operating may need to be registered with the system(or identifiable as an authorized apparatus and/or software) via theSystem Web site before it may be allowed to connect.

The following are exemplary Windows of the BCP 216 application that maybe available.

EGM Navigator: A list of EGMs 213 that can be selected or dragged ontoother windows.

Collection Navigator: List of named collections that have been saved.

Override Navigator: List of EGMs 213 with a current Manual override inaffect.

Assignment Navigator: List of assignments that have been saved.

Inventory Pane: Shows full details of one or more selected EGMs 213.

Find Results: Shows results of a search function.

Activity Pane: Shows a log of what has occurred since the applicationhas launched. May also provide access to transaction logs throughout thesystem for selected periods of time including tracing activity relatedto a specific EGM, specific server, or any other network-connecteddevice receiving and/or transmitting data or instructions.

Download Assignment Wizard: Allows user to specify a downloadassignment. For example, the download assignment wizard may have panessuch as: Identity, Packages, Schedule, and Review.

Configuration Assignment Wizard: Allows user to specify a configurationassignment. For example, the configuration assignment wizard may havepanes such as: Identity, Device Options, Game Bundles, Schedule, andReview.

Floor Layout: A visual representation of the floor that can be used fornavigation and selection in a manner equivalent to the EGM 213navigator.

Notifications Tab: List of notifications for the currently logged-inuser.

Schedule Tab: Allows user to review jobs, see their status and orprogress.

The application may also have a menu bar, toolbar, and status bar. Otherdialogs such as an about box, logon dialog, change password dialog anderror dialogs may be included.

In an example embodiment, the BCP 216 interacts directly with thefollowing Web-based services: Activity, User Authentication, Download,and Configuration.

In addition to the Web Services 223, the BCP 216 may require file systemaccess for local debug/trace logging. It may have no direct Databaseaccess. It may be capable of printing but does not require a printer toperform its functions. The BCP 216 uses the tradition .net processingmodel.

FIG. 19 shows an exemplary block diagram of a download handler 233,according to one illustrated embodiment. The responsibilities of theDownload handler 233 may include the following.

-   -   Poll for job requests    -   Translate job requests to G2S download class commands    -   Send G2S host command to destination EGMs 213    -   Process G2S command responses from EGMs 213    -   Process G2S events    -   Update job status    -   Update EGM State through Data Access Layer 222

In an example implementation, communication with EGM devices may beexclusively via G2S messages, and there may not be a connection with BCPor other clients which create work requests. The Download handler 233may be a .Net assembly. The assembly may be loaded by the G2S Engine 280and may run in the context of this process (service).

Subcomponent Description Configuration Private storage of settings,limits and constants Job Reader Poll work queue from data tier ProtocolTranslator Transform job context to G2S commands G2S Message Processresponses from EGMs to G2S host Handlers commands Event Handlers Processexceptions and state changes from EGMs Logging Output of event anddiagnostics Controller Controls the processing

The Download handler 233 may interact with the Data Tier 224, G2S Core,Activity (EGM events), and Microsoft Enterprise Library Loggingcomponents. In an example embodiment, there is no direct interactionto/from the end users. Job requests may be output to the database (DataAccess Layer 222) and polled by the Download component.

Example Resources for the Download Handler 233:

-   CPU The Download handler may not require a dedicated processor. CPU    utilization may be proportional to the quantity of messages    processed. The traffic pattern of download messages may be a “burst”    pattern where average/mean traffic is minimal, but peak message    rates can be high.    -   Generally, the Download handler may not require more than a        single processor, but during peak download message peaks the G2S        server may be processor constrained and enhancements may be        anticipated for the G2S Engine to scale the application across        multiple servers.-   Disk In an example embodiment, the download handler does not    directly access disk resources. The Download handler interfaces to    the Data Access Layer, Activity and Logging. Only minimal disk space    for the assembly file (All) may be required.-   Network In an example embodiment, the download handler does not    directly access network resources. The messages sent to/from EGMs    are normally small and don't consume significant network resources    apart from the bandwidth that may be required to download/update    package files from the Download Services Point.

The Data access layer 222 may store configuration and state informationfor the objects being managed by the download handler. Configurationfiles may be used to store all persistent data that is not stored in theData tier 224. The distinction between storing a value in theconfiguration files instead of adding the element to the Data accesslayer 222 database and interface(s) can be arbitrary. For example, ifthere is a requirement to limit the maximum size for a package, thisvalue could be added to the Data access layer 222, or stored in aconfiguration file.

The configuration files may include, but are not limited to, valuesfor: 1) settings required for testing; 2) limits and constraints; 3)constants.

The hierarchy for a value stored in a configuration data store may be:i) File; ii) Section; and iii) Key/Value pairs.

Programmatic access to the configuration files may, for example, be withthe Microsoft.Practices.EnterpriseLibrary.Configuration namespaceclasses. These classes allow a single application to use multipleconfiguration files, and for multiple applications to share commonconfiguration files. The details of the data store implementation arehidden from the Download component.

In an example embodiment, the Download handler 233 does not receive workrequests directly from the Control panel 216 (BCP) client or thescheduling component. These components add/modify job records in thedatabase via the Data Access Tier. The Download Service may have asubcomponent that will poll the job data via the Data Access Tier andupdate job status.

The interface between the Download Service and the Data tier 224 is aWeb service. The required methods for polling and updating the job datamay include: 1) GetJobList—A collection of all job requests. (The methodincludes filtering parameters.); 2) GetJob—Get a single job request; and3) UpdateJob—Change the status of a job request.

The G2S Core may provide communication between the Download Service andthe EGM 213 devices. Host commands may be sent from the Download Serviceto an EGM via the G2S Core Interface, and the G2S Core Interface mayprovide the response from the EGM 213. The G2S Core component(s) mayprovide persistent storage.

From G2S Message Protocol Download Class Draft v0.8 (hereby incorporatedby reference), the requirements implicitly mandate that this interfaceprovide the capability to send the following G2S host commands to anEGM:

-   -   Enable/Disable EGM download (setDownloadStatus)    -   Refresh EGM Enable/Disable State (getDownloadStatus)    -   Refresh EGM Download Profile (getDownloadProfile)    -   Download Package To EGM (addPackage)    -   Create Package For Upload (createPackage)    -   Upload Package From EGM (updatePackage)    -   Delete Package From EGM (deletePackage)    -   Refresh Package Status (getPackageStatus)    -   Refresh EGM Package List (getPackageContents)    -   Refresh all EGM Packages Status (getPackageList)    -   Refresh Package Log Status (getPackageLogStatus)    -   Refresh Current Package Log (getPackageLog)    -   Set EGM Package Installation Script (setScript)    -   Remove Script from EGMs List of Scripts (deleteScript)    -   Authorize Script (authorizeScript)    -   Refresh EGM Script Status (getScriptStatus)    -   Refresh EGM Script List (getScriptList)    -   Refresh EGM Script Log Status (getScriptLogStatus)    -   Refresh EGM Script Log (getScriptLog)    -   Refresh EGM Module List (getModuleList)

Each of the above G2S host commands may need a response and the serversystem 201 may utilize handler(s) to process the EGM 213 response.

The Download Service may “register” to receive the following Events: a)G2S_DLX (download exceptions). There are approximately 25 DLX events tobe handled, and b) G2S_DLE (download events). There are approximately 30DLE events to be handled.

The events indicate a change in the state of processing an SMP (ServiceManagement Platform) command by an EGM 213. The processing of theseevents will update the database via the Data Access Layer interface. Theprocessing actions are specified in the sequence diagrams for thedownload class commands.

The Data tier 224 provides an API (Application Program Interface)between the Download Service component and the database for storing theconfiguration/state information of the objects being managed by slotmanagement system 101, and the “job” information that is the primaryinput source for the Download Service. Because these two sets of dataobjects (i.e., config/state and job) may be loosely coupled, they may beimplemented as separate classes.

All download class command responses from the EGMs 213 may result in adatabase operation through the Data access layer 222, excluding eventclass commands, which may be processed through the Activity Interfaceindependently of the Download Service. The methods required maycorrelate directly with the EGM 213 command responses except as noted.The required methods for processing command responses from the EGM 213may include:

-   -   DownloadStatus    -   DownloadProfile    -   PackageStatus    -   PackageContents    -   PackageList (Collection of PackageStatus Nodes)    -   PackageLogStatus    -   PackageLogList    -   ScriptStatus    -   ScriptList    -   ScriptLogStatus    -   ScriptLog List    -   ModuleList

The implementation of the Data access layer 222 interfaces may be a“synchronous” transaction, meaning that the success/failure of thedatabase operation is included in the response.

In an example embodiment, some Business Rules include: a) an eventrecord may be created for every request/response process with an EGM,via the Activity Web Service 243; b) package sizes may be limited to aconfigurable maximum size; and c) the OptionConfig handler may replicatethe required EGM data from the Core database 231 to the Configurationdatabase 228 in order to support reporting.

The Download handler 233 may consist of a single .Net assembly file.This assembly may be deployed to the disk location required by the G2SEngine 280.

FIG. 20 shows an exemplary block diagram of a configuration handler 232,according to one illustrated embodiment. Example responsibilities of 15OptionConfig handler may include:

-   -   Received unsolicited messages from EGMs 213    -   Persist the data the from the unsolicited messages to the Config        Database    -   Manage and route G2S Messages    -   Process G2S command responses from EGMs 213    -   Process G2S events    -   Update job status

Example Constraints may include: a) the communication with EGM devicesmay be exclusively via G2S messages; and b) there may be no connectionwith BCP or other clients which create work requests.

Example Composition May Include:

Subcomponent Description Configuration Private storage of settings,limits and constants Job Reader Poll work queue from data tier ProtocolTranslator Transform job context to G2S commands G2S Message Processresponses from EGMs to G2S host Handlers commands Event Handlers Processexceptions and state changes from EGMs Logging Output of event anddiagnostics Controller Controls the processing

The OptionConfig Service component may interact with the Data tier 224,G2S Core and the Activity (EGM events) components. The Data access layer222 may store configuration and state information for the objects beingmanaged by slot management system 101.

Configuration files may be used to store all persistent data that is notstored in the Data tier 224. The distinction between storing a value inthe configuration files instead of adding the element to the Data AccessLayer database and interface(s) can be arbitrary. For example, if thereis a requirement to limit the maximum size for a package, this valuecould be added to the Data Access Layer, or stored in a configurationfile. The configuration files may include, but are not limited to,values for: 1) settings required for testing; 2) limits and constraints;and constants.

Programmatic access to the configuration files may be with the .NetFramework 2.0 System, incorporated by reference herein. Configurationnamespace classes and the Microsoft Practices, Enterprise, Library, andCommon Configuration classes, are all incorporated by reference herein.These classes allow a single application to use multiple configurationfiles, and for multiple applications to share common configurationfiles.

In an example embodiment, the Option Config handler does not receivework requests directly from the Control panel 216 (BCP) client or thescheduling component. These components add/modify job records in thedatabase via the Data Access Tier. The Download Service may have asubcomponent that will poll the job data via the Data Access Tier andupdate job status.

The interface between the Option Config Service and the Data tier 224may be a Web service. Methods for polling and updating the job data mayinclude: a) GetJobList—A collection of all job requests. (The methodincludes filtering parameters); b) GetJob—Get a single job request; andc) UpdateJob—Change the status of a job request.

The G2S Core may provide the communication between the Option 10 ConfigService and the EGM 213 devices. In which case, Host commands may besent from the Option Config Service to an EGM via the G2S Core.

According to some embodiments, the Option Config Service may “register”to receive the following Events: a) G2S_DLX (download exceptions). Forexample, there may be 25 DLX events to be handled; and b) G2S_DLE(download events). For example, there may be 30 DLE events to behandled.

The events may indicate a change in the state of processing an SMP(Service Management Platform) command by an EGM. The processing of theseevents will update the database via the data access layer 222 interface.The processing actions may be specified in the sequence diagrams for thedownload class commands.

The Data tier 224 provides an API (Application Program Interface)between the OptionConfig Service component and the database for storingthe configuration/state information of the objects being managed by slotmanagement system 101, and the “job” information that may be the primaryinput source for the Download Service. Because these two sets of dataobjects (config/state vs. job) may be loosely coupled, they may beimplemented as separate classes.

All Option Config class command responses from the EGMs 213 may resultin a database operation through data access layer 222. The methods maycorrelate directly with the EGM 213 command responses except asotherwise noted. According to one embodiment, the methods for processingcommand responses from the EGM 213 may include:

-   -   optionList    -   optionChangeStatus    -   setOptionConfigStatus    -   getOptionList    -   setOptionChange    -   cancelOptionChange    -   authorizeOptionChange    -   getOptionChangeLogStatus    -   getOptionChangeLog

FIG. 21 shows an exemplary block diagram of a scheduler service 221.According to one illustrated embodiment, the Scheduler (SchedulerService) 221 may be implemented as an executable program. According toone embodiment, there may be two types of Scheduling: DownloadScheduling and Config Scheduling.

Configuration assignments may be run in order by schedule type:Permanent, Permanent with start date, Re-occurring Override, and OneTime Override. Within a schedule type, the assignment with the earlierstart date may be initiated first. Within matching start dates,assignments having static collections may be initiated before dynamic;if still tied, those assignments with earlier create dates may beinitiated first. Configuration assignments of permanent and permanentwith start date may include static collections.

Download Scheduling gets the start date that download process begins. Itmay take an indeterminate amount of time for the downloaded package tobe ready to be installed on a given EGM. Also, to avoid downloadconflict, if multiple download assignments exist for the same moduletype on an EGM, the assignment with the latest creation date takesprecedence.

The Scheduler may be reliant upon the Schedule database 229.

Example Scheduler Composition May Include:

Subcomponent Description Error Handlers Process and gracefully handleexceptions Logging Output of event and diagnostics

Exemplary Interactions may include: 1) scheduler listens to Scheduledatabase 229; 2) scheduler interacts with Schedule Web service; 3) theWeb Service may, for example, include a Windows Server version 2000 or2003 (hereby incorporated by reference) with the following Windowscomponents running: a).net Framework version 2.0 and/or b) InternetInformation Server (IIS 260).

Processing—The Scheduler service 221 may query the Schedule database 229for jobs that are scheduled to be run. The Scheduler may initiate theprocessing of the jobs by notifying the GUI Download Web Service 262 orthe GUI Configuration Web Service 264.

Interface/Exports—The Scheduler service 221 may consume the Activity WebService 243 to log its processing events. The Scheduler service 221 mayalso interact with the Schedule SQL database with ActiveX Data Objects(ADO) commands.

FIG. 22 shows an exemplary block diagram of a user interface downloadWeb service 262 according to one illustrated embodiment.

Classification—Web Service

Definition—The Web Service may expose Web Methods to consumingcomponents to allow the interaction with the Download database 227.

The data access logic for the BCP 216 to interact with the Downloaddatabase 227 may be included within the Download Web service 236.

The GUI Download Web Service 262 may be responsible for interacting withthe Data tier 224 for those components that are consuming its exposedmethods.

The BCP 216 may consume this Web Service and utilize its Web Methods tocreate and read necessary Download data in the database.

The GUI Download Web Service 262 may be used by the BCP 216 as acommunication layer with the Download database 227.

Example Constraints may include: 1) consuming components may need tocommunicate via the Simple Object Access Protocol (SOAP) in order toconsume the Web Service; 2) the Web Service may publish a Web ServiceDescription Language (WSDL) to describe the Web service, the messageformat and protocol details; and 3) the Web Service may return itsrequested results in the form of a Serialized DataSet.

Example Compositions May Include:

Subcomponent Description SOAP Proxy Communication Data Access Processrequests made by consuming components by Handlers communicating with thedatabase with ActiveX Data Objects (ADO) logic Error Handlers Processand gracefully handle exceptions Logging Output of event and diagnostics

Example Interactions May Include:

The GUI Download Web Service 262 may interact specifically with theControl panel 216 (BCP) via Simple Object Access Protocol (SOAP).

The GUI Download Web Service 262 may interact with the Download SQLdatabase with ActiveX Data Objects (ADO) logic.

The Web Service may, for example, include a Windows Server version 2000or 2003 with the following Windows components running: a).net Frameworkversion 2.0 and/or b) Internet Information Server (IIS 260).

Processing—The GUI Download Web Service 262 may process requests made byconsuming components. The requests may be made by the consumingcomponent calling the GUI Download Web Service 262 exposed Web Methods.A successful request may be dependent upon the consuming componentcalling a Web Method by supplying the appropriate query parameters asdictated by the Web Service Description Language (WSDL) file. The WebService processes the request by executing its embedded Business Logicwhile logging exceptions and events. The resulting output is returned tothe consuming component.

Interface/Exports

The GUI Download Web Service 262 may consume the Activity Web Service243 to log its processing events. It may also interact with the DownloadSQL database with ActiveX Data Objects (ADO) commands. Its capabilitiesmay be exposed as Web Methods which are accessed via the Simple ObjectAccess Protocol (SOAP).

FIG. 23 shows an exemplary block diagram of a user interface 20configuration Web service, according to one illustrated embodiment.

Classification—Web Service

Definition—This Web Service may expose Web Methods to consumingcomponents to allow the interaction with the Configuration database 228.The data access logic used for the BCP 216 to interact with theConfiguration database 228 may be arranged within the Configuration Webservice 238.

The Configuration Web service 238 may be responsible for interactingwith the Data tier 224 for those components that are consuming itsexposed methods.

The BCP 216 may consume the Configuration Web service 238 and utilizeits Web Methods to create and read necessary Option Configuration datain the database.

The Configuration Web service 238 may be advantageously used by the BCP216 as a communication layer with the Configuration database 228.

Example Constraints may include: 1) consuming components may communicatevia the Simple Object Access Protocol (SOAP) in order to consume the WebService; b) the Web Service may publish a Web Service DescriptionLanguage (WSDL) to describe the Web service, the message format andprotocol details; and c) the Web Service may return its requestedresults in the form of a Serialized DataSet.

Example Composition May Include:

Subcomponent Description SOAP Proxy Communication Data Access Processrequests made by consuming components by Handlers communicating with thedatabase with ActiveX Data Objects (ADO) logic Error Handlers Processand gracefully handle exceptions Logging Output of event and diagnostics

Example Interactions May Include:

The GUI Configuration Web Service may interact with the Control panel216 (BCP) via Simple Object Access Protocol (SOAP).

The Configuration Web service 238 may interact with the ConfigurationSQL database with ActiveX Data Objects (ADO) logic.

The Web Service may, for example, include a Windows Server version 2000or 2003 with the following Windows components running: a).net Frameworkversion 2.0 and/or b) Internet Information Server (IIS 260).

The GUI Configuration Web Service may process requests made by consumingcomponents. The requests may be made by the consuming component callingthe GUI Configuration Web Services exposed Web Methods. A successfulrequest may be dependent upon the consuming component calling a WebMethod by supplying the appropriate query parameters as dictated by theWeb Service Description Language (WSDL) file. The Web Service processesthe request by executing its embedded Business Logic while loggingexceptions and events. The resulting output is returned to the consumingcomponent.

Example Interface/Exports May Include:

The GUI Configuration Web Service may consume the Activity Web Service243 to log its processing events. It may also interact with theConfiguration SQL database with ActiveX Data Objects (ADO) commands. Itscapabilities may be exposed as Web Methods which are accessed via theSimple Object Access Protocol (SOAP).

FIG. 24 shows an exemplary block diagram of a scheduler Web service 241,according to one illustrated embodiment.

Classification—Web Service

Definition—According to one embodiment, the scheduler Web service 241exposes Web Methods to consuming components to allow the interactionwith the Scheduler database. The data access logic used for theScheduler to interact with the Scheduler database may be included withinthe Scheduler Web service 241.

Exemplary Constraints may include: 1) consuming components maycommunicate via the Simple Object Access Protocol (SOAP) in order toconsume the Web Service; 2) the Web Service may publish a Web ServiceDescription Language (WSDL) to describe the Web service, the messageformat and protocol details; and 3) the Web Service may return itsrequested results in the form of a Serialized DataSet.

Example Composition May Include:

Subcomponent Description SOAP Proxy Communication Data Access Processrequests made by consuming components by Handlers communicating with thedatabase with ActiveX Data Objects (ADO) logic Error Handlers Processand gracefully handle exceptions Logging Output of event and diagnostics

Example Uses/Interactions May Include:

The Scheduler Web service 241 interacts specifically with the Schedulercomponent via Simple Object Access Protocol (SOAP).

The Scheduler Web service 241 interacts with the Scheduler SQL databasewith ActiveX Data Objects (ADO) logic.

Example platform for the Web Service may include a Windows Serverversion 2000 or 2003 with the following Windows components runninga).net Framework version 2.0 and/or b) Internet Information Server (IIS260).

Example Processing May Include:

The Scheduler Web service 241 may process requests made by consumingcomponents. The requests are made by the consuming component calling theScheduler Web service 241 exposed Web Methods. A successfully requestmay be dependent upon the consuming component calling a Web Method bysupplying the appropriate query parameters as dictated by the WebService Description Language (WSDL) file.

The Web Service may process the request by executing its embeddedBusiness Logic while logging exceptions and events. The resulting outputmay return to the consuming component.

Example Interface/Exports May Include:

The Scheduler Web service 241 may consume the Activity Web Service 243to log its processing events. It may also interact with the SchedulerSQL database with ActiveX Data Objects (ADO) commands. Its capabilitiesmay be exposed as Web Methods which are accessed via the Simple ObjectAccess Protocol (SOAP).

FIG. 25 shows an exemplary block diagram of an executive unit, accordingto one illustrated embodiment. According to one embodiment, theresponsibilities of the Executive component may include: 1) receive jobnotifications from the Scheduler; 2) determine destination G2S Host fora given EGM assignment; 3) deliver an assignment job to the destinationG2S Host; 4) receive status updates from G2S Hosts; 5) update jobassignment status in the data store (via Web Services 223 Tier); 6)manage workflow of job and job steps; and 7) automatic recovery of workflow processing upon start up.

Example Constraints may include: a) there may be no direct connectionwith the Presentation Layer (BCP) or EGM devices and/or b) inter servercommunications may be secure. For example, a Secure Sockets Label (SSL)Web service is one approach to provide secure communications.

Example Compositions May Include:

The Executive component may be multiple components. Deployment mayinclude an executable program deployed as, for example, a WindowsService, IIS 260 Web services deployed on the same server as the WindowsService, and IIS 260 Web services deployed on each G2S Host Server 211.

Subcomponent Description Job Creator Interface for receiving jobrequests. Transforms jobs to individual EGM Assignments and adds to theEGM 213 Assignment Queue for delivery to the destination EGM host.Assignment Reads the EGM 213 Assignment Queue. Determines Dispatcher theG2S Host currently providing the G2S Host device for a given EGM/Devicepair and delivers EGM assignment to that G2S Host. EGM Receive jobstatus updates and updates the device Assignment class database (e.g.,Config and Download) and notifies Status Reader the Workflow Manager ofthe status change. Workflow Determines changes to job status andassignment status Manager from the EGM 213 assignment status. Controlsthe order and flow of multi-sequence assignment jobs. DAL InterfacesEncapsulate database access to the job assignment data and EGM Coredata. G2S Executive Receives EGM assignment from the AssignmentInterface Dispatcher. The assignment is relayed to the G2S Host'sExecutive Queue, which is read by the G2S Host and forwarded to thedestination EGM. EGM Job Sends EGM status data from the G2S Host to theStatus Delivery Executive's EGM Assignment Status Reader. Logging Outputof event and diagnostics

Example Uses/Interactions May Include:

The Executive component interacts with the Scheduler, Data Tier WebServices, G2S Core, Activity (EGM events), and Logging components. Theremay be no direct interaction to/from the end users (Presentation Layer)or the EGM 213 devices.

The Executive may receive the following from the Scheduler via the JobReader interface: a) run new job (See e.g., FIG. 14 and FIG. 15) and/orb) cancel pending job (See e.g., FIG. 11 and FIG. 14).

Example Resources May Include:

-   CPU The traffic pattern of incoming requests is not expected to be    high and the processing requirements are minimal. This component may    not require a dedicated processor and should scale to 2500 EGMs    utilizing fewer than 20% CPU resources.-   Disk The Executive component may not directly access disk resources.    The interactions to data access layer 222, Activity and Logging may    require disk space, and the Scheduler queue and G2S Host queue, if    the quantity and size of the messages in these queues is not    significant. Only minimal disk space for the assembly file (.dll)    may be required.-   Database The Execute component may generate a small number of    database read, insert and update queries, the quantity of which is    proportional to the number of assignment operations.-   Network This component interacts with the Scheduler, G2S Host and    Web Services data tier across the network. The quantity of data for    all these transactions is small and should not create significant    traffic on the network.

Example Configuration Interfaces May Include:

Data access layer 222 may store configuration and state information forthe objects being managed by slot management system 101. Configurationfiles will be used to store all persistent data that is not stored inthe Data tier 224. The configuration files may include, but are notlimited to, values for: a) settings required for testing; b) limits andconstraints; and c) constants.

Configuration data values that may be shared across multipleapplications include: 1) executive host; 2) G2S host(s); 3) executivejob interface Uri (referenced by Scheduler); and 4) outbound G2S Hostjob queue (referenced by G2SHost) and/or 5) inbound G2S Host job statusqueue (referenced by G2SHost).

Programmatic access to the configuration files may be with theMicrosoft.Practices.EnterpriseLibrary.Configuration namespace classes.These classes allow a single application to use multiple configurationfiles and for multiple applications to share common configuration files.The details of the data store implementation are hidden from theExecutive component.

The configuration for the Job Reader Interface may be in thesystem.runtime.remoting section of the application configuration file.The Scheduler may require the client configuration, and the Executivemay use the service and channels configuration. The host name (or someform of identification) may be used for the client remotingconfiguration. If the Scheduler and Executive are not co-located on thesame server and failover is required then a virtual IP address or hostname in the client configuration may be used.

An Example Job Creator May be Incorporated as Follows:

The Executive receives job requests from the Scheduler via a Web serviceinterface. This Web service interfaces with the Job Creator componentand may comprise two methods of calls: RunJob and CancelJob. Theparameters may include the data that identifies the job.

The Job Creator reads the EGM 213 assignments comprising the job fromthe database via data access layer 222 subcomponents and outputs theindividual EGM assignments to the Assignment Dispatcher via a MessageQueue. The items in the queue are an internal representation of the EGM213 assignment. That is, the items may not be G2S messages or anystandard representation and may be consumed by internal components.

The Web service interface may be encapsulated into a proxy class whoseassembly may be used by the caller (Scheduler). The classes referencedby the interface may be in an assembly shared by both the Scheduler andExecutive classes.

The name of the EGM 213 Assignment message queue may be known to boththe Job Creator (writer) and Assignment Dispatcher (reader) and may beincluded in the configuration data store for the respective components.

An Example Assignment Dispatcher May be Incorporated as Follows:

The EGM 213 assignments created by the Job Creator are consumed by theExecutive service 220, transformed to the destination format anddispatched to the appropriate G2S Host which is providing G2S servicesto the destination host.

The destination information for the EGM 213 Assignment is determined bya database query via data access layer 222 subcomponents. Thedestination information includes the target server and deliverymethod/protocol (only G2S for this project).

The objects read from the EGM 213 Assignment Queue are transformed froman internal representation to the format required by the destination.For G2S, the delivery method is a Web service interface.

This interface to the G2S Host is encapsulated into a proxy class. Theclasses referenced by the interface will be in an assembly shared byboth the Assignment Dispatcher and Executive EGM Web service component.

An Example EGM Assignment Web Service May be Incorporated as Follows:

The G2S Host Handlers will send progress and/or completing status of theEGM 213 assignment to the Job Status Reader subcomponent. This interfacewill be a private Message Queue. The handlers write to this queue andthe EGM 213 Assignment Delivery component will read from the queue anddeliver to the Executive's Job Status Reader.

The EGM 213 Assignment Delivery component is a thread within the G2SHost and may require modification to the G2S Host to launch andterminate this thread.

This interface to the Job Status Reader is encapsulated into a 25 proxyclass. The classes referenced by the interface will be in an assemblyshared by both this component and the Job Status Reader.

An Example Job Status Reader May be Incorporated as Follows:

The Job Status Reader is the interface between the G2S Host's EGMAssignment Delivery and the Executive. This component updates the EGM213 Assignment status in the appropriate database(s), and notifies theWorkflow Manager of the state change.

The Job Status Reader is a Web service deployed on the same server asthe Executive service 220 to allow intra-server communication methods tothe Workflow Manager rather than requiring yet another Web serviceinterface.

An Example Workflow Manager May be Incorporated as Follows:

The Workflow manager may be responsible for determining when updating ajob's status based of the status of the EGM 213 assignments of which thejob is composed. For example, if there is an assignment for 5 EGMs 213,then after the fifth EGM assignment is at a terminal state then the jobstatus is at a terminal state.

The Workflow Manager will also contain business logic for controllingworkflow of multi-sequence job assignments with conditional logicbetween job assignment sequences. For example, a denomination change isexecuted after a game theme change is successfully completed.Conditional logic may not be within the scope of this project.

The Workflow Manager may be a thread within the Executive service 220.

An Example EGM Job Status Delivery May be Incorporated as Follows:

The G2S Host Handlers will send progress and/or completing status of theEGM 213 assignment to the Job Status Reader subcomponent. This interfacewill be a private Message Queue. The handlers write to this queue andthe EGM 213 Assignment Delivery component will read from the queue anddeliver to the Executive's Job Status Reader.

The EGM 213 Assignment Delivery component is a thread within the G2SHost and may require modification to the G2S Host to launch andterminate this thread.

This interface to the Job Status Reader may be encapsulated into a proxyclass. The classes referenced by the interface may be in an assemblyshared by both this component and the Job Status Reader.

An Example Activity Interface May be Incorporated as Follows:

The Executive may send log information to the Activity Recorder via theActivity Recorder Web Service. The interfaces implemented for the FloorSystem may be used and no enhancements are required.

An Example Data Access Layer Interfaces May be Incorporated as Follows:

The Data tier 224 provides an API between the Executive component andthe database for storing the configuration/state information of theobjects being managed by Download and Configuration server network 201,and the “job” information. While there are three separate databases, thedatabase may hide the details of the physical implementation from theExecutive.

The Executive may request or effectuate the following transactions viadata access layer 222: 1) query job assignments for a given schedule; 2)query EGM server identify given the EGM 213 ID and G2S host class; 3)update EGM Job status; 4) update Assignment Job status; and 5) get nextEGM Job step.

The implementation of data access layer 222 interface may be a“synchronous” transaction, meaning that the success/failure of thedatabase operation may be included in the response.

Example Business Rules may include an event record and may be createdfor every request read from the Job Reader interface.

Example Deployment Requirements may include the Executive being deployedin four separate components: 1) executive Windows Service, 2) executiveIIS 260 Web services (2), 3) G2S Executive IIS 260 Web service; and 4)G2S Host.

Configuration file(s) may also be used for the deployment.

FIG. 26 shows an exemplary block diagram of a download 5 handler Webservice, according to one illustrated embodiment.

Classification—Web Service

Definition—This Web Service may expose Web Methods to consumingcomponents to allow the interaction with the Download database 227. Thedata access logic required for the Download Handler to interact with theDownload database 227 is contained within the Download Handler WebService.

Example Constraints may include: a) consuming components may need tocommunicate via the Simple Object Access Protocol (SOAP) in order toconsume the Web Service; b) the Web Service may publish a Web ServiceDescription Language (WSDL) to describe the Web service, the messageformat and protocol details and/or c) the Web Service may return itsrequested results in the form of a Serialized DataSet.

Example Compositions May Include:

Subcomponent Description SOAP Proxy Communication Data Access Processrequests made by consuming components by Handlers communicating with thedatabase with ActiveX Data Objects (ADO) logic Error Handlers Processand gracefully handle exceptions Logging Output of event and diagnostics

Example Uses/Interactions May Include:

The Download Handler Web Service interacts specifically with theDownload Handler via Simple Object Access Protocol (SOAP).

The Download Handler Web Service interacts with the Download SQLdatabase with ActiveX Data Objects (ADO) logic.

Example Resources May Include:

The Web Service may utilize a Windows Server version 2000 or 2003platform with the following Windows components running: a).net Frameworkversion 2.0 and/or b) Internet Information Server (IIS 260).

Example Processing May Include:

The Download Handler Web Service processes requests made by consumingcomponents. The requests may be made by the consuming component callingthe Download Handler Web Services exposed Web Methods. A successfulrequest is dependent upon the consuming component calling a Web Methodby supplying the appropriate query parameters as dictated by the WebService Description Language (WSDL) file. The Web Service processes therequest by executing its embedded Business Logic while loggingexceptions and events. The resulting output is returned to the consumingcomponent.

Example Interface/Exports May Include:

The Download Handler Web Service may consume the Activity Web Service243 to log its processing events. The Download Handler Web Service mayalso interact with the Download SQL database with ActiveX Data Objects(ADO) commands. Its capabilities are exposed as Web Methods which areaccessed via the Simple Object Access Protocol (SOAP).

FIG. 27 shows an exemplary block diagram of an alternative configurationhandler Web service 239, according to one illustrated embodiment.

Classification—Web Service

Definition—This component may expose Web Methods to consuming componentsto allow the interaction with the Configuration database 228. The dataaccess logic required for the Configuration Handler 232 to interact withthe Configuration database 228 is contained within the ConfigurationHandler Web Service 239.

Example Constraints may include: a) consuming components may communicatevia the Simple Object Access Protocol (SOAP) in order to consume the WebService and/or b) the Web Service may publish a Web Service DescriptionLanguage (WSDL) to describe the Web service, the message format andprotocol details.

The Web Service may return its requested results in the form of aSerialized DataSet.

Example Compositions May Include:

Subcomponent Description SOAP Proxy Communication Data Access Processrequests made by consuming components by Handlers communicating with thedatabase with ActiveX Data Objects (ADO) logic Error Handlers Processand gracefully handle exceptions Logging Output of event and diagnostics

Example Uses/Interactions May Include:

The Configuration Handler Web Service 239 interacts with theConfiguration Handler 232 via Simple Object Access Protocol (SOAP).

The Configuration Handler Web Service 239 interacts with theConfiguration SQL database with ActiveX Data Objects (ADO) logic.

Example Resources May Include:

The Web Service may utilize a Windows Server version 2000 20 or 2003platform with the following Windows components running. a).net Frameworkversion 2.0 and/or b) Internet Information Server (IIS 260).

Example Processing May Include:

The Configuration Handler Web Service 239 may process requests made byconsuming components. The requests may be made by the consumingcomponent calling the Configuration Handler Web Services 239 exposed WebMethods. A successful request is dependent upon the consuming componentcalling a Web Method by supply the appropriate query parameters asdictated by the Web Service Description Language (WSDL) file. The WebService processes the request by executing its embedded Business Logicwhile logging exceptions and events. The resulting output is returned tothe consuming component.

Example Interface/Exports May Include:

The Configuration Handler Web Service 239 may consume the Activity WebService 243 to log its processing events. It may also interact with theConfiguration SQL database with ActiveX Data Objects (ADO) commands. Itscapabilities are exposed as Web Methods which are accessed via theSimple Object Access Protocol (SOAP).

FIGS. 28, 28B, and 28C show sequence diagrams of an exemplary viewpackage, view package modules, and view package management logs,according to one illustrated embodiment. Some examples of possiblemessage sequences are shown that may be used to accomplish the tasksdescribed herein. As most of the Control panel 216 driven user interfacetasks have similar sequences, a few have been shown to demonstrate theseveral sequences which are generalizable and representative of thevarious procedures available to a user. Web Services 223 may be designedwith fewer and chunkier messages than what might be done if these weresimple procedure or function calls. Thus the sequence may be one messagesuch as, for example, GetAssignmentData which would return a complex XMLresponse spelling out all the attributes of an assignment. Later the BCP216 may call SaveAssignment and pass the entire structure back withmodifications.

The SaveAssignment sequence may be created as part of a detailed designand implementation. The SaveAssignment sequence may serve as a bridgebetween the UI and the database, both of which have been specified indetail herein.

Other sequences in this section document the message flow between theHost and an EGM. These have been implemented for all major use cases asthis is an external integration point. While the G2S protocol documentsmay specify how these should work, they are often open to multipleinterpretations. These sequences allow the iView and Alpha teams tocompare their expectations with ours and give the whole team a chance toresolve differences earlier in the development cycle when it is cheaper.

An example Verify Package (described in FIG. 4) Sequence may include:

The Verify Package use case may perform verification and authenticationon the Software Download Distribution Point (SDDP 252). It may use anencryption algorithm that is stored on a read-only media so that theregulators can place a tape seal over the media to prevent anyunauthorized DVD/CD into the media.

There may be two actors who can perform the verification process. Thefirst actor may be a user on the BCP 216 with the security role of theApprover. That user can initiate a verification process on demand fromthe GUI interface. The second actor may be the Host System which may bea scheduled task that runs the verification process once every 24 hours.

The verification process may be to read an encryption algorithm andcontent hash values from a read-only media and perform the algorithm onthe content server to produce new hash values. Then the two hash valuesmay be compared with each other to detect if the content has beentampered with. The results from the verification process may be loggedto the database so that audit reports can be run that show when theprocess was initiated, by whom, and what the results were. Theverification process may also report if any un-authorized files havebeen copied to the Software Download Distribution Point.

FIGS. 29-46 show exemplary sequence diagrams, according to someillustrated embodiments.

FIGS. 47A and 47B show exemplary sequence diagrams of a packagemanagement process and a package management system configuration,according to one illustrated embodiment.

Example Package Management Sequences May Include:

This sequence diagram depicts the four major steps that may be done toinstall a package from read only drive (DVD Drive 276) to SDDP server252 disk.

1) Obtaining SDDP server 252 Disks list: To allow users to choose thedestinations of a package, obtaining SDDP server 252 disks list sequencediagram shows the steps to be implemented to request SDDP server 252disks list from core database 231 and send the result back to PackageManagement GUI 274, so that the user may select appropriate destinationdisk.

2) Verifying Hash Codes: Before copying a package from read-only driveto SDDP server 252 disks the validity of the package may be verified.The verifying hash codes process may compare the hash code which may beone of the read-only drive with another hash code that may be availablein the package drive, and may verify that those two are identical.

3) Storing Package Info: In this process the package info which mayinclude the hash code and may be stored in Download database 227. Also,the path of SDDP server 252 disk may be stored in this database.

4) Copying Package: In this process the package may be copied from theread-only drive to SDDP server 252 disk.

In one embodiment, the read only drives may be in the same machine whichruns the Package Management GUI 274. Also, SDDP server 252 disks pathsmay be hard-coded in Package Management GUI 274 (Console Application).Connections to databases may be through Download GUI Web Service 262.

FIGS. 48A-48L show an example block diagram of a download 5 ERD databaseorganization, according to one illustrated embodiment.

Example Data View—Download

The download database 227 may encapsulate all the storage needed tosupport the download component of the system. It may hold the currentinventory of all EGMs 213 as discovered via the G2S protocol (which ishereby incorporated) via the communications and download classes. It maystore the assignments used to change that inventory via download classcommands. It may store job state information for the jobs thoseassignments use to carry out downloads and installations. And it maystore the inventory of the SDDP 252.

Download may be coupled directly or indirectly to the Schedule and Coredatabases 231. It leverages schedule to store assignment schedules fordownload and install and to queue pending jobs. It references core toreplicate basic EGM information and to manage EGM collections. As withat least some components, activity history may be posted to the activitydatabase 230 through Web Services 223 and may be stored locally in alimited fashion.

G2S may use the concept of scripts to install downloads and specify theapprovals and other conditions that must be met for an install to occur.In the Download Database 227 the Script table with its related commandtables may be linked to an assignment. When a script is sent to anindividual EGM to be used, the script data from these tables may be usedas a template to create the ScriptStatus and related Command Statustables. The ScriptStatusID may be used as the script ID in the setScriptcommand. Status for this script may be tracked within these ScriptStatus tables and the rows may be used for that instance of the script.

Data Dictionary

Example JobQueue:

Hold jobs that are waiting to be run. Scheduler may poll this table andkick off jobs when the start time has passed. If the schedule is tied toa job that is recurring, then once the current instance succeeds, thescheduler may create a new row in this table for the next occurrence ofthe job using the same parameter data as the current job.

QueuedDateTm datetime Date time job placed in queue PrevCalledDateTmdatetime Date time last attempt to call Web method occurredNextCalIDateTm datetime Date time that this job is meant to be run. Jobis run by calling the Web method. CallSucceeded tinyint Defaults 0. Setto 1 when call succeeds and scheduler can purge this record. ScheduleIDint FK to schedule record this job is controlled by JobQueueID intIdentity PK QueuedDateTm datetime Date time job placed in queueMaxRetries int Max retries scheduler should attempt when Web service isunavailable, 0 if no retries Retries int Number of re-tries attempted.Set to 1 only after the first retry RetryIntervalSeconds int Number ofseconds between retries ParamData xml Parameter to pass to Web serviceWebServiceURI varchar URI of Web service to call WebMethod varchar Webmethod on service to call

Example Schedule:

Hold schedule records may be used by any parts of the system that storesa schedule. In one embodiment, simple schedule types with a start datemay be supported. In another embodiment, recurring tasks may also besupported.

DateCreated datetime Date record created in DB ScheduleTypeID int FK tothe type of schedule ScheduleID int Identity PK EndDateTm datetimeOptional end date and time StateDateTm datetime Start date and time

Example ScheduleType:

Hold schedule records may be used by any parts of the system that storesa schedule. In one embodiment, simple schedule types with a start datemay be supported. In another embodiment, recurring tasks may also besupported.

Description varchar Description of the schedule type ScheduleTypeID intIdentity PK ScheduleType varchar Permanent, PermanentVVithStart,OneTimeOverride, RecurringOverride

Example Assignment:

Data for what, when, and who is to download or install.

Deleted tinyint NULL DateTmDeleted datetime NULL TimeStmp timestamp NULLActive tinyint 1 is active and will be applied to floor. 0 is not activeApproved tinyint 1 is approved. Must be approved and active to takeeffect Name varchar Assignment name. DateCreated datetime Date theassignment was created. DateTmUpdated datetime Date the assignment waslast updated. DateTmApproved datetime date time approved SetSelectionvarchar Defines the selection range for options. (0 all, 1 intersection,2 union) CoreCollectionID int FK to Associated collection of EGMsDownloadScheduleID int FK to download schedule for assignmentInstallScheduleID int FK to install schedule for assignment AssignmentIDint Identity PK UpdateUserName varchar Login name of the user who lastupdated the assignment. ApproveUserName varchar login name of user whoapproved assignment Type varchar Type of assignment. Configuration orDownload Description varchar User entered description of the assignment

Example AssignmentJob:

Storage for state and status associated with an assignment job.

DateCreated datetime DateTime record created DateTmUpdated datetimeDateTime Status list updated AssignmentID int FK to Assignment for Job.0 or more Jobs per Assignment AssignmentJobID int Identity PK JobStatevarchar Queued, InProgress, Complete JobSummary varchar Text tosummarize jobs status for GUI. i.e., 4 of 5 EGMs completed without error1 of 5 not found.

Example AssignmentPackage:

One or more packages that are part of this assignment.

AssignmentID int NULL PackageID int NULL

Example CoreEGM:

EGM data ISplicated as encountered in messages from Core

DateTmUpdated datetime NULL DownloadEnabled tinyint 1 if the downloadclass functionally is enabled for the EGM 213, 0 otherwise AssetNumbervarchar Asset number as replicated from Core BankCode varchar Bank Codeas replicated from Core GSAEGMID varchar EGM ID used by GSA G2S messagesManufacturer varchar EGM Manufacturer Code replicated from Core SerialNumber varchar EGM Serial Number replicated from Core LocationCodevarchar Location Code as replicated from Core CoreEGMID int Same valueas replicated from the Core DB ZoneCode varchar Zone Code as replicatedfrom Core

Example EGMJob:

Sub-job of assignment job that applies to a particular EGM

CommandID bigint CommandID of last command sent. This will be returnedin the response. JobData xml Data containing state needed to carry outjob - define by job type DateCreated datetime DateTime record createdDateTmUpdated datetime DateTime Status last updated JobCompleteStatevarchar Error or Success. Should we have a look up table? CoreEGMID intFK to EGM for this Job EGMJobID int Identity PK JobState varchar Queued,InProgress, Complete. Should we have a look-up table? JobSummary varcharText to summarize jobs status for GUI. (e.g., 4 of 5 EGMs completedwithout error 1 of 5 not found.) TransactionID bigint Transaction IDsent by EGM in response to command. Used to tie events to commands.

Example EgmPackage:

Packages that may be on an EGM. From the PackageList response.

CoreEgmID int NULL PackageID int NULL PackageState varchar NULLInstallStartDateTm datetime NULL InstallEndDateTm datetime NULL

Example Package:

Data about a package in the SDDP.

PackageID int NULL GSAPackageID varchar NULL Description varchar NULLType varchar NULL Location varchar NULL PackageDescriptor xml NULLGSAManufacturerID char Manufacturer identifier.

Example ScheduleSchedule:

Replicated data from the Schedule table in the Schedule database 229that allows for enforcing RI locally.

ScheduleScheduleID int ID of the corresponding schedule record in theSchedule database.

FIGS. 49A-49I show an exemplary block diagram of a configuration ERDdatabase organization or tree, according to one illustrated embodiment.

Example Configurations May Include:

The configuration database 228 may encapsulate all the storage needed tosupport the option configuration component of the system. It holds thecurrent option configuration of all EGMs 213 as discovered via the G2Sprotocol in the communications, optionConfig, and gamePlay classes. Thisincludes options items for ordinary devices and games which are known inthe protocol as game play devices. It also stores the potential oravailable option item choices for each EGM. It stores the assignmentsused to change options item values via optionConfig class commands. Andit stores job state information for the jobs those assignments use tocarry out option changes.

Configuration may be directly or indirectly coupled to the Schedule andCore databases 231. It leverages schedule to store assignment schedulesand to queue pending jobs. It references core to replicate basic EGMinformation and to manage EGM collections. As with all other components,activity history may be posted to the activity database 230 through WebServices 223 and may be stored locally.

Example Configuration Database Dictionary

AllowedEGMTheme AllowedEGMThemeID int NULL AllowedEGMTheme CoreEGMID intAssociated EGM identifier. AllowedEGMTheme Theme varchar Associated gametheme identifier. AllowedThemeDenom AllowedEGMThemeID int NULLAllowedThemeDenom Denom int NULL AllowedThemeDenom AllowedThemeDenomIDint Primary key allowable EGM denomination, e.g., 5 cents.AllowedThemePaytable AllowedThemePayTableID int NULLAllowedThemePaytable AllowedEGMThemeID int NULL AllowedThemePaytablePayTable varchar NULL Assignment DateTmDeleted datetime NULL AssignmentTimeStmp timestamp NULL Assignment Deleted tinyint NULL AssignmentActive tinyint 1 is active and will be applied to floor. 0 is not activeAssignment Approved tinyint 1 is approved. Must be approved and activeto take effect Assignment Name varchar Assignment name. AssignmentDateCreated datetime Date the assignment was created. AssignmentDateTmUpdated datetime Date the assignment was last updated. AssignmentDateTmApproved datetime date time approved Assignment ManageGameOptionstinyint Defines if the assignment is managing game combos. AssignmentSetSelection varchar Defines the selection range for options. (0 all, 1intersection, 2 union) Assignment CoreCollectionID int FK to associatedcollection of EGMs Assignment ScheduleID int FK to schedule forassignment Assignment AssignmentID int Identity PK AssignmentApproveUserName varchar login name of user who approved assignmentAssignment UpdateUserName varchar Name of the user who last updated theassignment. Assignment Type varchar Type of assignment. Configuration orDownload Assignment Description varchar User entered description of theassignment AssignmentAvailableGamePlayDevice Active tinyint 1 means theassignment is meant to make this an active game on the EGM 213AssignmentAvailableGamePlayDevice AssignmentID int FK to assignment forthis GamePlayDevice AssignmentAvailableGamePlayDeviceAllowedThemePaytableID int FK to Paytable for this GamePlayDeviceAssignmentAvailableGamePlayDevice AllowedEGMThemeID int FK to Theme forthis GamePlayDevice AssignmentAvailableGamePlayDeviceAssignmentAvailableGamePlayDeviceID int Identity PKAssignmentAvailableGamePlayDeviceDenom AssignmentGamePlayDeviceDenomIDint NULL AssignmentAvailableGamePlayDeviceDenomAssignmentAvailableGamePlayDeviceID int NULLAssignmentAvailableGamePlayDeviceDenom Denom int NULL AssignmentJobDateCreated datetime DateTime record created AssignmentJob DateTmUpdateddatetime DateTime Status last updated AssignmentJob AssignmentID int FKto assignment for Job. 0 or more Jobs per assignment AssignmentJobAssignmentJobID int Identity PK AssignmentJob JobState varchar Queued,InProgress, Complete AssignmentJob JobSummary varchar Text to summarizejobs status for GUI. i.e., 4 of 5 EGMs completed without error 1 of 5not found. AssignmentOptionItem AssignmentOptionItemID int NULLAssignmentOptionItem AssignmentID int NULL AssignmentOptionItemOptionItemDefinitionID int NULL AssignmentOptionItemValueAssignmentOptionItemValueID int NULL AssignmentOptionItemValueAssignmentOptionItemID int NULL AssignmentOptionItemValue AssignedValuevarchar NULL CoreCollection CoreCollectionID int ID of the collection inthe Core Database CoreEGM DateCreated datetime NULL CoreEGMDateTmUpdated datetime NULL CoreEGM OptionConfigEnabled tinyint 1 if theoptionConfig class functionality is enabled for the EGM 213, 0 otherwiseCoreEGM AssetNumber varchar Asset number as replicated from Core CoreEGMBankCode varchar Bank Code as replicated from Core CoreEGM GSAEGMIDvarchar EGM ID used by GSA G2S messages CoreEGM Manufacturer varchar EGMManufacturer Code replicated from Core CoreEGM SerialNumber varchar EGMSerial Number replicated from Core CoreEGM LocationCode varchar LocationCode as replicated from Core CoreEGM CoreEGMID int Same value asreplicated from the Core DB CoreEGM ZoneCode varchar Zone Code asreplicated from Core EGMAvailableGamePlayDeviceEGMAvailableGamePlayDeviceID int NULL EGMAvailableGamePlayDeviceCoreEGMID int NULL EGMAvailableGamePlayDevice AllowedEGMThemeID int NULLEGMAvailableGamePlayDevice AllowedEGMPaytableID int NULLEGMAvailableGamePlayDevice Active tinyint NULLEGMAvailableGamePlayDevice AssignedActive tinyint NULLEGMGamePlayDeviceDenom EGMGamePlayDeviceDenomID int NULLEGMGamePlayDeviceDenom EGMAvailableGamePlayDeviceID int NULLEGMGamePlayDeviceDenom Denom int NULL EGMJob AssignmentJobID int NULLEGMJob CommandID bigint CommandID of last command sent. This may bereturned in the response. EGMJob JobData xml Data containing state usedto carry out job - define by job type EGMJob DateCreated datetimeDateTime record created EGMJob DateTmUpdated datetime DateTime Statuslast updated EGMJob JobCompleteState varchar Error or Success. EGMJobCoreEGMID int FK to EGM for this Job EGMJob EGMJobID int Identity PKEGMJob JobState varchar Queued, InProgress, Complete. EGMJob JobSummaryvarchar Text to summarize jobs status for GUI, i.e., 4 of 5 EGMscompleted without error 1 of 5 not found. EGMJob TransactionID bigintTransaction ID sent by EGM in response to command. Used to tie events tocommands. OptionDevice deviceID int Device ID as reported by optionListcommand OptionDevice CoreEGMID int FK to EGM this device was reportedwith via optionList. 1 or more devices per EGM OptionDevice deviceClassvarchar G2S class enumeration value like G2S_cabinet or G2S_gamePlayOptionDevice OptionDeviceID int Identity PK OptionDevice DateCreateddatetime Rows in this table are never modified so we only keep createdate OptionGroup DateCreated datetime DateTime record createdOptionGroup OptionDeviceID int FK to device this group belongs to. 1 ormore groups per device. OptionGroup GroupProtocolID varchar ID of groupas defined by protocol OptionGroup OptionGroupID int Identity PKOptionGroup GroupProtocolName varchar Name of group as defined byprotocol OptionGroup DateTmUpdated datetime Updates would only occur ifname changes for a give ID OptionItemAssignedValueOptionItemDefinitionID int 1 or more assigned values may exist for thereferenced definition OptionItemAssignedValue AssignmentID intAssignment for which value was derived OptionItemAssignedValueDateTmAssigned datetime DateTime of update OptionItemAssignedValueOptionItemAssignedValueID int Identity PK OptionItemAssignedValueAssignedValue varchar Value the system calculated that the EGM 213should currently have for this item. It may not match current until thesetChange operation succeeds OptionItemCurrentValue DateTmUpdateddatetime NULL OptionItemCurrentValue OptionItemDefinitionID int 1 ormore current values may exist for the referenced definitionOptionItemCurrentValue CurrentValue varchar Current Value of this itemas reported by EGM OptionItemCurrentValue OptionItemCurrentValueID intIdentity PK OptionItemDefaultValue DateTmUpdated datetime NULLOptionItemDefaultValue OptionItemDefinitinonID int 1 or more defaultvalues may exist for the referenced definition OptionItemDefaultValueOptionItemDefaultValueID int Identity PK OptionItemDefaultValueDefaultValue varchar The default value as reported by EGMOptionItemDefinition OptionProtocolID varchar NULL OptionItemDefinitionOptionProtocolName varchar NULL OptionItemDefinition OptionHelp varcharNULL OptionItemDefinition OptionType varchar NULL OptionItemDefinitionSecurityLevel varchar NULL OptionItemDefinition CanModEgm tinyint NULLOptionItemDefinition CanModHost tinyint NULL OptionItemDefinitionMinValue numeric NULL OptionItemDefinition MaxValue numeric NULLOptionItemDefinition FractionaIDigits int NULL OptionItemDefinitionMinLength int NULL OptionItemDefinition MaxLength int NULLOptionItemDefinition CurrencyID varchar NULL OptionItemDefinitionDenomID numeric NULL OptionItemDefinition ExchangeRate numeric NULLOptionItemDefinition MinSelections int NULL OptionItemDefinitionMaxSelections int NULL OptionItemDefinition Duplicates tinyint NULLOptionItemDefinition DateCreated datetime NULL OptionItemDefinitionDateTmUpdated datetime NULL OptionItemDefinition OptionGroupID int Groupthis item belongs to. 1 or more items per group. OptionItemDefinitionOptionItemDefinitionID int Identity PK OptionItemEnum EnumValue varcharA possible legal value for this referenced definition. OptionItemEnumOptionItemDefinitionID int FK to the related Option Item Definition.OptionItemEnum OptionItemEnumID int Identity PK OptionItemOverrideValueOptionItemOverrideValueID int NULL OptionItemOverrideValueOptionItemDefinitionID int NULL OptionItemOverrideValue OverrideValuevarchar NULL OptionItemOverrideValue DateTmOverriden datetime NULLScheduleSchedule ScheduleScheduleID int ID of the corresponding schedulerecord in the Schedule database.

FIG. 50 shows an exemplary block diagram of the schedule database 229,according to one illustrated embodiment.

An Example Schedule Database 229 May Include:

The schedule database 229 may have a few tables which reflect its scope.It may support functions, such as storing schedule data for other systemcomponents as needed, and kicking off jobs at the scheduled time forthose components. Jobs are kicked off by calling the Web serviceprovided with the parameter data provided at the time a job isregistered with the scheduler.

The schedule databases and corresponding sub-system may be looselycoupled. Its reference to data in other components may be indirect viathe Web method references it stores, or it may be directly coupled torespective components. As with other components, activity history may beposted to the activity database 230 through Web Services 223 and may bestored locally.

An Example Schedule Database Dictionary May Include:

An example JobQueue that may Hold jobs that are waiting to be run.Scheduler may poll this table and kick off jobs when the start time haspassed. If the schedule a job is recurring, then once the currentinstance succeeds, the scheduler will create a new row in this table forthe next occurrence of the job using the same parameter data as thecurrent job.

QueuedDateTm datetime Date time job placed in queue PrevCalledDateTmdatetime Date time last attempt to call Web method occurredNextCalIDateTm datetime Date time that this job is meant to be run. Jobis run by calling the Web method. CallSucceeded tinyint Defaults 0. Setto 1 when call succeeds and scheduler can purge this record. Schedule IDint FK to schedule record this job is controlled by JobQueueID intIdentity PK MaxRetries int Max retries scheduler should attempt when Webservice is unavailable; 0 if no retries Retries int Number of re-triesattempted. Set to 1 only after the first retry RetryIntervalSeconds intNumber of seconds between retries ParamData xml Parameter to pass to Webservice WebServiceURI varchar URI of Web service to call WebMethodvarchar Web method on service to call

An example Schedule that may Hold schedule records used by any parts ofthe system that stores a schedule. In one embodiment, simple scheduletypes with a start date may be supported. In another embodiment,recurring tasks may also be supported.

DateCreated datetime Date record created in DB ScheduleTypeID int FK tothe type of schedule Schedule ID int Identity PK EndDateTm datetimeOptional end date and time StateDateTm datetime Start date and time

An example ScheduleType may Hold schedule records used by any parts ofthe system that stores a schedule. In one embodiment, simple scheduletypes with a start date may be supported. In another embodiment,recurring tasks may also be supported.

Description varchar Description of the schedule type ScheduleTypeID intIdentity PK ScheduleType varchar Permanent, PermanentWithStart,OneTimeOverride, RecurringOverride

FIGS. 51A-51Z show exemplary diagrams of menu screens for a 15 controlpanel 216, according to one illustrated embodiment.

Example User Interfaces—Control Panel 216:

The client may encapsulate all the functionality to support the commandand control portions of the download and configuration features of theproject. Downloads and configuration options can be scheduled, ordeployed immediately. Notifications, approvals, searches, and reports inthese areas can be viewed.

Control panel—login to control panel. A user can change the passwordthrough a login password menu.

FIG. 51D shows an example list of EGMS 213 that may be selected ordragged onto other Windows, according to one illustrated embodiment.

FIG. 51E shows an example Collection Navigator menu is shown thatincludes a List of named collections that have been saved, according toone illustrated embodiment.

FIG. 51F shows an example Assignment Navigator menu is shown thatincludes a List of assignments that have been saved, according to oneillustrated embodiment.

FIG. 51G shows an example Manual Override Navigator menu is shown thatincludes a List of EGMs 213 with a current Manual override in effect,according to one illustrated embodiment.

FIG. 51H shows an example Inventory menu that lists the full details ofa currently selected EGM, according to one illustrated embodiment. FIG.51I shows an example Search menu that presents the results of a searchfunction, according to one illustrated embodiment.

FIG. 51J shows an example Activity Log query and display which displaysa record of what has occurred since the application was launched,according to one illustrated embodiment.

FIG. 52A-D shows an example set of Download Assignment Wizard menus suchthat the wizard will let the user specify a download assignment,according to one illustrated embodiment. In one embodiment, it may have:Identity, packages, schedule, and review panes.

A Download Assignment Wizard may be included to pop-up and provide userswith helpful tips or ask if the user needs assistance and then direct auser to a menu of information, similar to the Microsoft Windows Wizard.This feature can be disabled by a user, either by closing the Wizarddisplay or selecting disablement from an options menu.

FIG. 53A-E show an example set of Configuration Assignment Wizard menussuch that the wizard may let the user specify a configurationassignment, according to one illustrated embodiment. In one embodiment,it may have: Identity, device options, game bundles, schedule, andreview panes.

Similar to the Download Assignment Wizard, a Configuration AssignmentWizard may be included to assist users.

FIG. 54A shows an exemplary floor layout panel that provides a visualrepresentation of the floor that can be used for navigation andselection by a user with the BCP in a manner equivalent to the EGM 213navigator, according to one illustrated embodiment.

FIG. 54B shows an exemplary schedule menu and display that lets userreview jobs, see their status and/or progress, according to oneillustrated embodiment.

FIG. 54C shows an example tasks list display and menu that provides alist of tasks where the currently logged in users are displayed,according to one illustrated embodiment. This window may have threepanels indicating notifications, pending tasks, and completed tasks.When applicable the user may click on it and obtain more details abouteach task. Controls may be utilized to acknowledge notifications and tomark tasks complete.

FIG. 55 shows an exemplary casino floor display providing a visualrepresentation of the casino floor, according to one illustratedembodiment.

FIG. 56 shows an exemplary schematic illustration of a casino networkincluding corporate, back-office and floor networks, according to oneillustrated embodiment.

FIG. 57 shows a method 5700 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 5702, a download and configuration management system determines arelatively optimal one of a plurality of download distribution pointsgeographically distributed throughout the at least one casino propertyfor at least one of the gaming machines. At 5704, the download andconfiguration management system provides an indication to the at leastone of the gaming machines that indicates the relatively optimal one ofthe download distribution points to be used by the at least one of thegaming machines to download configuration instructions.

FIG. 58 shows a method 5800 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 5802, the download and configuration management system determines arelatively optimal one of the download distribution points based atleast in part on a physical location of the download distribution pointswith respect to a physical location of the at least one of the gamingmachines. For example, the download and configuration management systemmay determine that the optimal one of the download distribution pointsis the download and distribution point that is geographically closest tothe particular gaming machine(s), or the one of the downloaddistribution points that has the desired downloadable instructions thatis geographically closest to the gaming machine(s).

FIG. 59 shows a method 5900 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 5902, the download and configuration management system determines arelatively optimal one of the download distribution points based atleast in part on an availability of respective ones of the downloaddistribution points with respect to an availability of other ones of thedownload distribution points. Thus, the download and configurationmanagement system may take into account a current availability, avoidingdelays that might otherwise result from using a download distributionpoint that is already busy downloading to other gaming machines. Indoing so, the download and configuration management system may also takeinto account whether the download distribution points have the desireddownloadable instructions that are geographically closest to the gamingmachine(s).

FIG. 60 shows a method 6000 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 6002, the download and configuration management system determines arelatively optimal one of the download distribution points based atleast in part on a connection speed between respective one of thedownload distribution points and the at least one gaming machinerelative to a connection speed between other ones of the downloaddistribution point and the at least one gaming machine. Thus, at 5902,the download and configuration management system may avoid delays byaccounting for differences in connection speeds. In doing so, thedownload and configuration management system may also take into accountwhether the download distribution points have the desired downloadableinstructions that are geographically closest to the gaming machine(s).

FIG. 61 shows a method 6100 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 6102, the download and configuration management system determines arelatively optimal one of the download distribution points for acollection of the gaming machines, where each of the collection ofgaming machines include at least two different ones of the gamingmachines. Thus, gaming machines may be grouped or otherwise placed intocollections or sets. The gaming machines may, for example, be grouped bygame type, manufacturer, and or version. The gaming machines may, forexample, be grouped by type of hardware installed in the gaming machinesand/or by the type of firmware or software, or by a version of thefirmware or software. This may advantageously simplify the configurationand management of the gaming machines.

FIG. 62 shows a method 6200 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 6202, the download and configuration management system determines arelatively optimal one of the download distribution points based on acombination of a connection speed between respective ones of thedownload distribution points and the at least one gaming machinerelative to a connection speed between other ones of the downloaddistribution point and the at least one gaming machine and anavailability of respective ones of the download distribution points withrespect to an availability of other ones of the download distributionpoints. As previously noted, the download and configuration managementsystem may also take into account whether the download distributionpoints have the desired downloadable instructions that is geographicallyclosest to the gaming machine(s).

FIG. 63 shows a method 6300 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 6302, the download and configuration management system provides anindication to the at least one of the gaming machines that indicates therelatively optimal one of the download distribution points to be used bythe at least one of the gaming machines to download configurationinstructions, for example by providing an Internet protocol address.Such causes the gaming machines to look to the identified downloaddistribution point for configuration and downloads of instructions(e.g., software, firmware).

FIG. 64 shows a method 6400 of operating a download and configurationmanagement system to manage a plurality of gaming machines distributedthroughout at least one casino property, according to one illustratedembodiment.

At 6402, the download and configuration management system caches aplurality of packages of instructions at the plurality of downloaddistribution points. The packages of instructions are downloadable tothe gaming machines to redefine the operation of the gaming machines.Some of the packages of instructions may be cached by less then all ofthe download distribution points. Consequently, there may be identicalpackages located at two or more download distribution points, althoughthere may be download distributions points that do not each have thesame packages of instructions.

At 6404, the download and configuration management system storesinformation at the download and configuration management serverindicative of which of the packages of instructions are available atwhich of the download distribution points. Such may allow the downloadand configuration management server to determine a most optimal one ofthe download distribution points since the download and configurationmanagement server can determine if the particular download distributionpoints has a certain or desired package of instructions.

Example Reports software configuration and download project reports mayprovide real-time and historical data. An example embodiment providesfor Download and Configuration reports to be run on an inter/intranetbrowser, such as on SSRS. Windows authentication may be used forsecurity. In other embodiments, the reports may also or alternatively berun from the BCP. The download reports may include reports in theReports Detail Section. In addition, reports from the Floor System maybe imported into the Download and Configuration project in order for theDownload and Configuration applications to run independently of thefloor system. One or more of the databases from the Floor System may beincluded as well.

An example Detailed Reports Design may include reports which aregenerated through and/or based upon the Software Download FRD 2.8 (whichis 10 hereby incorporated by reference) and the G2S specifications.

Example User Reports May Include:

User Listing with Roles and Group—This report may be written for theFloor System project and may be imported from that project.

Password to Expire in 15 days—This report may be written for the FloorSystem project and may be imported from that project.

Role with Capabilities—This report may be written for the Floor Systemproject and may be imported from that project.

User Activity Role—This report may be written for the Floor Systemproject and may be imported from that project.

Assignment Reports—These reports may be provided to show lists ofassignments with summary information. Details reports are also availablefor detailed assignments. They can include the history of the jobs thathave been run on behalf of that assignment.

Example Package Assignment by EGM—Summary May Include:

Input Parameters: Start Date to End Date range for Package Create Date.

Logo: Tech Logo

Title: Package Assignment by EGM—Summary

Columns:

Group: Site Name

Group: EGM Group

Detail:

Package ID, Assignment ID, Module ID, Component, 5 Created Date, CreatedBy, Approved Date, Approved By, Total packages assigned, Total EGMs

Group By: Site, EGM Group (Collection)

Sort By: Package ID, Module ID

Sub-Total field: (Example dynamic groupings/collections) Sub:TotalColumns:

(Example dynamic groupings/collections)

Group Total field: Site Name

Group Total Columns: Total packages assigned, Total EGMs Grand Total?Yes

Grand Total Columns: Total packages assigned, Total EGMs

An Example Package Assignment by EGM—Detail May Include:

Input Parameters: [Start Date] to [EndDate] range for Package CreateDate

Logo: Tech Logo

Title: Package Assignment by EGM—Summary

Columns

Group: Site Name

Group: EGM Group

Detail:

EGM ID, Package ID, Assignment ID, Module ID, Component ID, CreatedDate, Created By, Approved Date, Approved By, Total packages assigned,Total EGMs

Group By: Site, EGM Group (Collection)

Sort By: EGM Internal Identifier, Package ID, Module ID

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: Site Name

Group Total Columns: Total packages assigned, Total EGMs

Grand Total? Yes

Grand Total Columns: Total packages assigned, Total EGMs

Example Module Assignment by EGM—Summary May Include:

Input Parameters: [Start Date] to [EndDate] range for AssignmentApproved Date

Logo: Tech Logo

Title: Module Assignment by EGM—Summary

Columns

Group: Site Name

Group: EGM Group

Detail: Module ID, Package ID, Assignment ID, Component ID, Created 10Date, Created By, Approved Date, Approved By, Total packages assigned,Total EGMs

Group By: Site, EGM Group (Collection)

Sort By: Module ID, Package ID

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: Site Name

Group Total Columns: Total packages assigned, Total EGMs

Grand Total? Yes

Grand Total Columns: Total packages assigned, Total EGMs

An Example Module Assignment by EGM—Detail May Include:

Input Parameters: [Start Date] to [EndDate] range for AssignmentApproved Date

Logo: Tech Logo

Title: Module Assignment by EGM—Summary

Columns

Group: Site Name

Group: EGM Group

Detail:

EGM ID, Module ID, Package ID, Assignment ID, Component ID, CreatedDate, Created By, Approved Date, Approved By

Group By: Site, EGM Group (Collection)

Sort By: EGM Internal Identifier, Module ID, Package ID

Sub-Total field: EGM Group

Sub:Total Columns: Total packages assigned, Total EGMs

Group Total field: Site Name

Group Total Columns: Total packages assigned, Total EGM Groups, TotalEGMs

Grand Total? Yes

Grand Total Columns: Total packages assigned, Total EGM Groups, TotalEGMs

An example User Assignments by Module may include:

Input Parameters: Start Date to End Date range for Assignment ApprovedDate

Logo: Tech Logo

Title: User Assignments by Module

Columns

Group: Site Name

Group: User

Detail:

User Name, User ID, Module ID, Package ID, Assignment ID, Component ID,Created Date, Created By, Approved Date, Approved By

Group By: Site, User Name

Sort By: Module ID

Sub-Total field: EGM Group

Sub:Total Columns: Total modules assigned

Group Total field: Site Name

Group Total Columns: Total modules assigned

Grand Total? Yes

Grand Total Columns: Total modules assigned,

An example Assignment History may include:

Input Parameters: Start Date to End Date range for Assignment ApprovedDate

Logo: Tech Logo

Title: Assignment History

Columns

Group: Site Name

Detail:

User Name, User ID, Module ID, Package ID, Assignment ID, Component ID,Created Date, Created By, Approved Date, Approved By

Group By: Site

Sort By: Assignment Date Created, Module ID Sub-Total field: N/A

Sub:Total Columns: N/A

Group Total field: Site Name

Group Total Columns: Total modules assigned

Grand Total? Yes

Grand Total Columns: Total modules assigned,

Job Reports

Example Job Status History by Assignment may include:

Input Parameters: Start Date to End Date range for Job Submit Date

Logo: Tech Logo

Title: Job Status History by Assignment

Columns

Group: Site Name

Group: Job ID

Detail:

Assignment, Job ID, Package ID, Component ID, Submit Date, Submitted By,Complete Date, Status

Group By: Site, Assignment ID

Sort By: Submit Date

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: Site Name

Group Total Columns: Total assignments

Grand Total? Yes

Grand Total Columns: Total packages assigned

An example Job Status History by EGM may include:

Input Parameters: [Start Date] to [EndDate] range for Job Submit Date

Logo: Tech Logo

Title: Job Status History by Assignment

Columns

Group: Site Name

Group: EGM

Detail:

Assignment ID, Job ID, Package ID, Component ID, Submit Date, SubmittedBy,

Complete Date, Status

Group By: Site, EGM

Sort By: Job ID, Submit Date

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: Site Name

Group Total Columns: Total assignments

Grand Total? Yes

Grand Total Columns: Total packages assigned

An example Failed Job History may include:

Input Parameters: [Start Date] to [EndDate] range for Job Submit Date

Internal Select: ‘Failed’ Job Status

Logo: Tech Logo

Title: Job Status History by Assignment

Columns

Group: Site Name

Group: Assignment ID

Detail: Assignment ID, Job ID, Package ID, Component ID (DownLoad) or

OptionItemID(Config), Submit Date, Submitted By, Event, Event Date

Group By: Site, EGM

Sort By: Job ID, Submit Date, event, event date

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: Site Name

Group Total Columns: Total Failed Jobs

Grand Total? YES

Grand Total Columns: Total Failed Jobs

Example Audit Reports may include:

1) User Activity;

2) EGM Activity;

3) Activity Report for Regulators;

4) Module Inventory;

5) List of Revoked/Outdated Packages;

6) Detailed EGM Job;

7) Failed EGM Job and/or

8) List of Revoked/Outdated Packages.

Example EGM Reports May Include:

EGM Device Inventory Report

This report may be written for the Floor System project and may beimported from that project.

EGM Event

This report may be written for the Floor System project and may beimported from that project.

EGM Meter

This report may be written for the Floor System project and may be 10imported from that project.

EGM Daily Financial (audited data)

This report may be written for the Floor System project and may beimported from that project.

EGM Listing

This report may be written for the Floor System project and may beimported from that project.

EGM Media

This report may be written for the Floor System project and may beimported from that project.

EGM Game Theme

This report may be written for the Floor System project and may beimported from that project.

Example EGM Group Reports may include:

Input Parameters: [Start Date] to [EndDate] range for Group Create Date

Internal Select: n/a

Logo: Tech Logo

Title: EGM Groups

Columns

Group: Site Name

Group: EGM Group

Detail:

1^(st) header line: EGM ID, Manufacturer ID, Install Date, GameCombinations

2^(nd) header line: Game Theme, PayTable, Denomination

Group By: Site, EGM Group

Sort By: EGM ID, Game Theme, Paytable, Denom

Sub-Total field: n/a

Sub:Total Columns: n/a

Group Total field: n/a

Group Total Columns: n/a

Grand Total? n/a

Grand Total Columns: n/a

- - -

APPENDIX Definitions, Acronyms, and Abbreviations Definition, Acronym,Abbreviation Description Control Panel (BCP) This smart clientencapsulates all the functionality to support the command and controlportions of the download and configuration features of the project. LiveServices These are the windows services which are responsible forexecuting the Business Logic of the system. Business Logic Layer TierThe Business Logic Layer is comprised of the Download and ConfigurationWindows Services which are responsible for implementing the BusinessLogic of the system. Database SQL Server 2005 returns information basedon the results of retrieving data from the following databases CoreConfiguration Download Activity Schedule Database Web Services These arethe Web services that will be able to be re-used by other GUI andService Applications in slot management system 101. Data Access LayerTier The Data Access Layer is comprised of Web Services which exposemethods for interacting with the Data Tier. EGM Tier The Data Tier iscomprised of Electronic Game Machines (EGM) and other configurablecomponents like iView and Game Controllers. Electronic Gaming MachineGaming machines and/or tables which may include electo- (EGM) mechanicaldevices and/or video displays. G2S (Game to System) The G2S (Game toSystem) protocol provides a messaging standard, using XML, forcommunications between gaming devices (such as game software, meters,and hoppers) and gaming management systems (such as progressives,cashless, and accounting). G2S Engine This service will receive G2Smessages from the EGM 213 and dispatch them to the Live Service based onthe message component type. G2S Download Protocol The G2S downloadprotocol will provide a standardized protocol to manage the downloadedcontent on all G2S compliant EGM from all G2S compliant host systems.G2S Message Command messages sent to an EGM to update or configure theEGM 213. G2S optionConfig Protocol The G2S optionConfig protocol willdownload options available from within and EGM. The SDDP server willmaintain all down load software packages in a secure library with arequired number of secure backups as defined by the jurisdiction. G2SEngine Tier The G2S Engine Tier is comprised of the G2S enginecomponents. Its job is to send and receive G2S protocol messages to andfrom EGM and other configurable devices. It is also responsible for thepackaging and unpacking of the internal system messages and G2S protocolmessages. iView Proprietary device for player touch point services. Itis used to display marketing and player tracking information. While notcurrently capable of “gaming,” it likely will be downstream, so it istreated herein as an EGM. Module A manufacturer-defined element that isa uniquely identifiable unit within the EGM. For example: A module canbe an operating system, or a game theme, firmware for a printer; etc. Amodule may be a single WAV sound file that is shared by other modules.Presentation Tier The Presentation Tier is comprised of the ControlPanel application. The Control Panel application is the GraphicalInterface through which the Download and Configuration portion of theLive system is managed. SDDP Server Will maintain all download softwarepackages in a secure library with a required number of secure backups asdefined by the jurisdiction. package A manufacturer-defined element thatcan be thought of as a single file, which contains: an optional downloadheader that contains information about the package payload. The packagepayload, with the payload being a ZIP file, TAR file, an XMLconfiguration file, a single BIN file, or any file format that makessense. The point is that the specific format of the payload is of nointerest to the command and control of the transfer. Software downloadThe ability to send packages between a Software Download DistributionPoint and one or more EGMs.

The above description of illustrated embodiments, including what isdescribed in the Abstract, is not intended to be exhaustive or to limitthe embodiments to the precise forms disclosed. Although specificembodiments of and examples are described herein for illustrativepurposes, various equivalent modifications can be made without departingfrom the spirit and scope of the disclosure, as will be recognized bythose skilled in the relevant art. For instance, the foregoing detaileddescription has set forth various embodiments of the devices and/orprocesses via the use of block diagrams, schematics, and examples.Insofar as such block diagrams, schematics, and examples contain one ormore functions and/or operations, it will be understood by those skilledin the art that each function and/or operation within such blockdiagrams, flowcharts, or examples can be implemented, individuallyand/or collectively, by a wide range of hardware, software, firmware, orvirtually any combination thereof. In one embodiment, the presentsubject matter may be implemented via Application Specific IntegratedCircuits (ASICs). However, those skilled in the art will recognize thatthe embodiments disclosed herein, in whole or in part, can beequivalently implemented in standard integrated circuits, as one or morecomputer programs running on one or more computers (e.g., as one or moreprograms running on one or more computer systems), as one or moreprograms running on one or more controllers (e.g., microcontrollers) asone or more programs running on one or more processors (e.g.,microprocessors), as firmware, or as virtually any combination thereof,and that designing the circuitry and/or writing the code for thesoftware and or firmware would be well within the skill of one ofordinary skill in the art in light of this disclosure. It will also beappreciated that many of the methods or processes may omit some acts,include additional acts, and/or may perform the acts in a differentorder than described herein, so long as the desired end result orfunctionality is achieved.

In addition, those skilled in the art will appreciate that themechanisms as taught herein are capable of being distributed as aprogram product in a variety of forms, and that an illustrativeembodiment applies equally regardless of the particular type of signalbearing media used to actually carry out the distribution. Examples ofsignal bearing media include, but are not limited to, the following:recordable type media such as floppy disks, hard disk drives, CD ROMs,digital tape, and computer memory; and transmission type media such asdigital and analog communication links using TDM or IP basedcommunication links (e.g., packet links).

Referring now to FIG. 65, a typical client-server architecture systemwith multiple clients requesting information from a server is shown. Ina strict client-server system, the server never initiates any messages.Accordingly, any messages the server sends to the client are in responseto a client's prior request. Thus, a problem arises if the serverbecomes aware of something that has changed in the system and it needsto notify one or more of the clients of the change, which the client(s)would likely be interested in knowing. While a client could “poll” theserver, this is an inefficient use of resources and a poor architecturaldesign. A preferred embodiment, uses a modified form of the UDP (UserDatagram Protocol) multicast protocol to implement a one-waynotification system 6500 and method between the server 6502 (e.g., DCM(Download and Configuration Manager) engine) and one or more clients6504 (e.g., Bally Control Panel (BCP)). UDP is a connectionless protocolthat runs on top of IP network, and offers a direct way to send andreceive datagrams over an IP network.

The UDP multicast notification system 6500 enables UDP messages to besent only to registered clients, not broadcasted to all clients. Thisarchitecture minimizes network traffic and enhances system security,since only registered clients receive the UDP message. The configurationof the UDP multicast notification system 6500 is relatively easy anddoes not require the configuration of network devices in order tosupport a UDP multicast. Furthermore, any number of the clients 6504 maybe on a different network domain than the DCM engine 6502. Each of theclients 6504 contains a display 6506 (e.g., user interface) on which theUDP messages are displayed.

FIGS. 65 and 66 illustrate one embodiment of the UDP multicastnotification system 6500. As shown in FIG. 65, a change has occurred todatabase table-1 and database table-4. In this specific non-limitingembodiment, BCP client-1 has registered to receive notificationsconcerning table-4, so a notification message is only sent to BCPclient-1. Additionally, in this specific, non-limiting embodiment, BCPclient-2 and BCP client-n have registered to receive notifications aboutchanges to database table-1. As such, FIG. 65 shows a notificationregarding database table-1 being sent to only clients 2 and “n.”Continuing, FIG. 66 shows the UDP multicast notification system 6500being used to send job status updates to BCP clients 2 and ‘n’ since the“Job Status” GUI (graphic user interface) is displayed on theirmonitors. In this embodiment, the GUI on BCP client-1 does not involvejob status information so BCP client-1 is not interested in Job Status.Thus, BCP client-1 does not get sent Job Status notification messages.

Referring now to FIG. 67, in this embodiment the UDP Broadcast Processor6512 is displayed as one component in the DCM engine 6502. The UDPBroadcast Processor 6512 is responsible for sending UDP messages to theregistered clients 6504 in the network 6510. In one embodiment, the UDPBroadcast Processor 6512 sends UDP messages to all registered clients6502 which are listening to receive UDP messages on a specific port.This enables one-way, server-to-client(s), communications in what isotherwise a strict client-to-server-to-client architecture by using theUDP multicast notification system 6500.

FIG. 68 illustrates the client registration process. Implementation ofthe UDP multicast notification system 6500 begins with a clientapplication (which in one embodiment is the BCP) sending a registrationmessage to the DCM engine 6502 with its IP address in the message. Inone embodiment, as shown in FIG. 68, the registration message alsoincludes what types of notifications the client 6504 wants to receive.The client 6504 then requests the port number from the DCM engine 6502,and the DCM engine responds with the port number on which the client6504 should listen.

FIG. 69 illustrates the process of sending a notification message, andmore specifically, illustrates the process that occurs when the DCMengine 6502 wants to send out a notification message. In one embodiment,the UDP broadcast processor 6512 queries the database 6514 for a list ofclients 6504 that have registered for a particular type of notification.The database 6514 then replies with the list. The UDP broadcastprocessor 6512 then formats and sends the notification to all clients6504 on the list using the assigned port number.

FIG. 70 illustrates the process of un-registering a client 6504 from theUDP multicast notification system 6500. Otherwise stated, FIG. 6displays the message sequence that occurs when a client wants to“unregister” from the UDP multicast notification system 6500. If a userterminates the BCP client application, the client 6504 asks the DCMengine 6502 to un-register it from the UDP multicast notification system6500. This includes deleting the client's IP address from the database6514.

Finally, it is to be appreciated that the invention has been describedhereabove with reference to certain examples or embodiments, but thatvarious additions, deletions, alterations and modifications may be madeto those examples and embodiments without departing from the intendedspirit and scope of the disclosed embodiments. For example, any elementor attribute of one embodiment or example may be incorporated into orused with another embodiment or example, unless to do so would renderthe embodiment or example unpatentable or unsuitable for its intendeduse. Also, for example, where the steps of a method are described orlisted in a particular order, the order of such steps may be changedunless to do so would render the method unpatentable or unsuitable forits intended use. All reasonable additions, deletions, modifications andalterations are to be considered equivalents of the described examplesand embodiments and are to be included within the scope of the followingclaims.

The various embodiments described above are provided by way ofillustration only and should not be construed to limit the disclosedembodiments. Those skilled in the art will readily recognize variousmodifications and changes that may be made to the disclosed embodimentswithout following the example embodiments and applications illustratedand described herein, and without departing from the true spirit andscope of the disclosed embodiments, which is set forth in the followingclaims.

1. A method for implementing a modified form of User Datagram Protocol(UDP) multicast notification system in a client-server architecture thatotherwise allows only client-initiated messages, the method comprising:receiving a registration message at a server from a client with a clientIP address in the registration message, wherein the registration messageincludes types of notifications desired to be received by the client,and wherein the server is a Download and Configuration Management (DCM)engine; adding the client IP address to a list in a registration messagedatabase; receiving a request for a port number by the client; andresponding with the port number to the client.
 2. The method of claim 1,wherein the clients are control panel applications.
 3. The method ofclaim 2, wherein the control panel applications are installed on controlstations.
 4. The method of claim 3, wherein the control stations areutilized in a casino gaming environment.
 5. The method of claim 3,wherein the control stations are utilized for downloading andconfiguration of games and/or game operating systems of connected gamingdevices.
 6. The method of claim 1, wherein the DCM engine communicateswith a database containing UDP multicast notification system data. 7.The method of claim 1, wherein the DCM engine includes DCM engineservices, business libraries, and a data access layer.
 8. The method ofclaim 7, wherein the DCM engine services include a user interfacenotification processor and a UDP broadcast processor.
 9. A system forimplementing a modified form of User Datagram Protocol (UDP) multicastnotification system in a client-server architecture that otherwiseallows only client-initiated messages, the system comprising: aplurality of clients configured in a client-server architecture; and aserver including one or more processors executing software instructionsthat perform the steps of: receiving a registration message from aclient with a client IP address in the registration message, wherein theregistration message includes types of notifications desired to bereceived by the client, and wherein the server is a Download andConfiguration Management (DCM) engine; adding the client IP address to alist in a registration message database; receiving a request for a portnumber by the client; and responding with the port number to the client.10. The system of claim 9, wherein the clients are control panelapplications.
 11. The system of claim 10, wherein the control panelapplications are installed on control stations.
 12. The system of claim11, wherein the control stations are utilized in a casino gamingenvironment.
 13. The system of claim 11, wherein the control stationsare utilized for downloading and configuration of games and/or gameoperating systems of connected gaming devices.
 14. The system of claim9, wherein the DCM engine communicates with a database containing UDPmulticast notification system data.
 15. The system of claim 9, whereinthe DCM engine includes DCM engine services, business libraries, and adata access layer.
 16. The system of claim 15, wherein the DCM engineservices include a user interface notification processor and a UDPbroadcast processor.
 17. A system for implementing a modified form ofUser Datagram Protocol (UDP) multicast notification system in aclient-server architecture that otherwise allows only client-initiatedmessages, the system comprising: means for receiving a registrationmessage at a server from a client with a client IP address in theregistration message, wherein the registration message includes types ofnotifications desired to be received by the client, and wherein theserver is a Download and Configuration Management (DCM) engine; meansfor adding the client IP address to a list in a registration messagedatabase; means for receiving a request for a port number by the client;and means for responding with the port number to the client.